Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

65 or more control mappins error #210

Closed
libertyrock opened this issue Mar 9, 2021 · 8 comments
Closed

65 or more control mappins error #210

libertyrock opened this issue Mar 9, 2021 · 8 comments
Labels
bug Something isn't working

Comments

@libertyrock
Copy link

prueba error realearn.zip

===== ATTENTION =====

Sorry, an unknown error occurred in REAPER plug-in ReaLearn. REAPER should continue to work but ReaLearn might show unexpected behavior until restarting REAPER. If you feel like saving your project file at this point, better save it as a new file because this error could have messed up the plug-in state.

In any case, please report this error:

  1. Prepare an e-mail containing:
    • The error information further below (IMPORTANT)
    • Some instructions on how to reproduce the error (IMPORTANT)
  2. If possible, attach the following files:
    • Your REAPER project file (.rpp)
    • Your REAPER configuration file (reaper.ini)
  3. Send it to info@helgoboss.org

Thank you for your support!

--- cut ---
Module name: ReaLearn
Module version: v2.5.0/x86_64 rev 225add (2021-03-03 13:15:42 UTC)
Module base address: 0x7ff94a7b0000
Module size: 0xc31000

Message: called Result::unwrap() on an Err value: "Full(..)"

0: 0x7ff94af5025d - Extended
1: 0x7ff94af4e779 - Extended
2: 0x7ff94ae37e9f - MAIN
3: 0x7ff94af70f30 - Extended
4: 0x7ff94af70a01 - Extended
5: 0x7ff94af6ddbf - Extended
6: 0x7ff94af70959 - Extended
7: 0x7ff94af89d90 - rust_eh_personality
8: 0x7ff94af89bf3 - rust_eh_personality
9: 0x7ff94a98268a - NSEEL_HOSTSTUB_EnterMutex
10: 0x7ff94a9819d0 - NSEEL_HOSTSTUB_EnterMutex
11: 0x7ff94a97b828 - NSEEL_HOSTSTUB_EnterMutex
12: 0x7ff94a97ad24 - NSEEL_HOSTSTUB_EnterMutex
13: 0x7ff94ac3be8c - DllMain
14: 0x7ff94aea3ebf - Run
15: 0x1402ba8cc -
16: 0x1401c9459 -
17: 0x1401c8433 -
18: 0x140400d31 -
19: 0x7ff99ffd2920 - ScreenToClient
20: 0x7ff99ffd20c2 - ScreenToClient
21: 0x7ff9a0019f99 - UnpackDDElParam
22: 0x7ff99ffce858 - CallWindowProcW
23: 0x7ff99ffce299 - DispatchMessageW
24: 0x1403fa5b1 -
25: 0x1408e2241 -
26: 0x7ff99ee07034 - BaseThreadInitThunk
27: 0x7ff9a08bd241 - RtlUserThreadStart
--- cut ---

@helgoboss
Copy link
Owner

Thanks for the report. This is a known issue 2.6.0 issue (see REAPER forum). In the meanwhile go back to 2.5.0.

@helgoboss
Copy link
Owner

Oh sorry, no ;) The opposite. It should be fixed in 2.6.0 but 2.6.0 has another issue. Will try to push out 2.7.0 today haha.

@libertyrock
Copy link
Author

ok...thanks

@helgoboss
Copy link
Owner

Have to correct myself again. This looks similar to another error but is different.

Do you use a particularly large project? Many tracks? Or did you disable ReaLearn instances? Wonder how you run into this error.

@helgoboss helgoboss added the bug Something isn't working label Mar 9, 2021
@helgoboss
Copy link
Owner

I could reproduce this error in a special case: If the audio device is stopped. Was your audio device stopped? I'll try to fix this.

@libertyrock
Copy link
Author

When executing an action it gives an error but if I remove up to 65 controllers it does not give it
Audio stopped

@libertyrock
Copy link
Author

Ocurrs when focus is in title bar of reaper window or mixer window

helgoboss added a commit that referenced this issue Mar 9, 2021
in order to be able to easily add protective measures if audio not running,
to not blow up the real-time channel
helgoboss added a commit that referenced this issue Mar 9, 2021
@helgoboss
Copy link
Owner

This particular channel exhaustion (indicated by the term "Full" in the error message) should be fixed in upcoming version 2.7.0. Other channel exhaustions might come up but then they deserve a new issue.

helgoboss added a commit that referenced this issue Mar 9, 2021
Also don't let mutex poisoning panics hide the original panic. Might be interesting for finding
the actual cause of #144.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants