You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
For some reason Reaper keeps crashing randomly as far as I can tell due to BYOD, since it says an instance of the plugin has crashed the next time I start reaper up (I could just be dumb and. I can't seem to narrow down one specific thing that is causing it to break, but the log files all say something similar to this with some slight variations each time:
Plugin crashing!!!
The crash in this log file is now being examined!
I'm not entirely sure what is causing the error or how to easily replicate it, and admittedly don't have enough coding experience to understand what the error is trying to say, but above it it does say something about the state containing processors that are currently locked, however the preset I am using does not contain any of the ones it lists. I also just updated to the most recent nightly build to see if that solved it but had no luck.
Windows 10
Reaper v6.77
64 bit
The text was updated successfully, but these errors were encountered:
Thanks for the descriptive bug report! I believe there was something that changed in a more recent version of Reaper, which triggers some different behaviour when the spacebar is pressed. I'll update my version of Reaper, and should be able to do some debugging later today.
Hmm, so I've been having some trouble re-creating the crash with Reaper v6.78. Would it be possible to try updating Reaper and seeing if the crash still occurs? If the crash still happens, would it be possible to share a small example project that crashes somewhat reliably? Ideally the project would not use any third-party plugins except for BYOD, to help isolate the issue.
Describe the bug
For some reason Reaper keeps crashing randomly as far as I can tell due to BYOD, since it says an instance of the plugin has crashed the next time I start reaper up (I could just be dumb and. I can't seem to narrow down one specific thing that is causing it to break, but the log files all say something similar to this with some slight variations each time:
Interrupt signal received!
Stack Trace:
3: UnhandledExceptionFilter + 0x1e7
4: memset + 0x13b0
5: _C_specific_handler + 0x96
6: _chkstk + 0x11f
7: RtlRaiseException + 0x434
8: RtlRaiseException + 0x185
9: RaiseException + 0x69
10: CxxThrowException + 0x90
30: ScreenToClient + 0xbc0
31: ScreenToClient + 0x362
32: UnpackDDElParam + 0x959
33: CallWindowProcW + 0x3f8
34: DispatchMessageW + 0x259
37: BaseThreadInitThunk + 0x14
38: RtlUserThreadStart + 0x21
Plugin crashing!!!
The crash in this log file is now being examined!
I'm not entirely sure what is causing the error or how to easily replicate it, and admittedly don't have enough coding experience to understand what the error is trying to say, but above it it does say something about the state containing processors that are currently locked, however the preset I am using does not contain any of the ones it lists. I also just updated to the most recent nightly build to see if that solved it but had no luck.
Windows 10
Reaper v6.77
64 bit
The text was updated successfully, but these errors were encountered: