Raven Locks up on Mojave on Cubase 9.5.5 - Reboot to Close

Thanks for your response Jamey. I'm still trying some things to see if I can clear up whatever is causing the lockup. I will lean on the support link if I need to though. I trying different sequences of when I open and close projects while Raven is open, along with closing Raven when I close projects (which would be annoying if that was the solution). I'm trying to first see what sort of behavioral protocol may be causing or leading to the lockup.

I will try to quit it via the OS X Activity Monitor next time it happens. The last time it happened I was trying to Force Quit via the "Force Quit" option from the Apple drop menu.

By the way, I did have another question pop in my head while I had your attention...

When I upgrade to Cubase 10.5 will I need to pay for another Raven license?

Thanks again, and I will let you know how far I get figuring it out.

Linenoise

Awesome, with regard to the license!

Regarding the lockup issue; I'm wondering if it's a Cubase crashing issue, because the last couple times I got the following:

- Raven prompt pops up asking if I want to save my Raven Session, as though I had told Raven to close, which I didn't;
- Then immediately after that, a crash report notification for Cubase pops up.

- I opened the crash report and saw that the crash of the Cubase app was due to a "EXC_BAD_ACCESS," which basically means that Cubase was sending a message to an object that has already been released. That is the common scenario for this error, but there are exceptions that I'm not knowledgeable enough in programming world to discuss or relay. But Essentially, there seems to be a misallocation of object references in either memory or CPU processing. I can't be sure.

- The other thing about that type of exception error is that it won't crash the app right away until the app tries to re-access that object that is no longer accessible, which may explain why the Raven prompt appeared first. Who knows...

- I will also note that it didn't lockup the Raven app when this happened last couple of times. I simply said "No" to saving the Raven session and after I relaunched Cubase I clicked the Raven icon in the task bar to open the Raven control surface with the Cubase environment. 

I'll attach the popups and the notable error log section after the prompts... No need to start a support ticket just yet. Just observing when events happens and what the results are.

Linenoise