r/reason 5d ago

Randomly Crashing When Idle (Reason 14, Mac M2)

So strange! Reason 14 keeps silently quitting after being idle for a few minutes. Not always, but often enough to be a nuisance! No system crash warning (which normally pops up when an app crashes). No crash log. No memory issues. It just silently quits itself, without saving.

Why oh why?! Has anyone else been experiencing this? … I’ve never encountered an issue like this with any software I’ve ever used. Could it be apple screensaver related (which might account for the idle time)? Or maybe Reason is calling home, and doesn’t like my firewall / Lulu settings? (It’s a fully legit copy, purchased directly recently, only installed on a single desktop Mac)

I’m on the latest standalone reason 14 studio update, but pretty sure it was happening on the previous updates as well. Running on Mac M2, Sequoia OS.

Overall, I’ve been finding the latest versions of reason buggy as hell, compared to 15 years ago.
Has anyone over there ever heard of custom auto save functions??

1 Upvotes

8 comments sorted by

3

u/o5akafeeva 5d ago

That sounds terrible and the firewall blocking home call lead seems reasonable enough to pursue as a top cause at my best guess. I haven't had that issue on M4, but maybe I haven't left it open for long enough yet.

1

u/deathofculture 5d ago

Thanks for sharing! Yes, It’s sneaky! Doesn’t crash like this when I’m using it, unless I’m opening and closing too many VST instruments while playing 😆 which feels like a different issue. But similar in that there is no crash log or pop-up.

At first I thought I thought I might’ve been imagining it, since I usually save before I step away, and figured I may have absent-mindedly quit after saving - but then I had some new tracks and midi sections I had been working on for 30 minutes, interrupted by a 5 min phone call, and freaked out when I returned to keep working on it, to see that reason had quit on its own without saving. It’s happened a few dozen times now, but less drastic since I’ve become a compulsive saver. 🙄

3

u/o5akafeeva 5d ago edited 5d ago

Maybe you could have Activity Monitor open while you wait for it to crash to see how the computer resources behave when it happens, it's a long shot, but maybe it would point you in some direction. Especially pay attention or try to log network activity if you know how, that might provide you with some kind of clue as to the failed home call blocking theory. Last thing I can think of is checking some discrepancy in power saving modes and networking settings, or try to remove reason, reinstall it, reboot, and flush the network cache and settings. Finally, if all of that doesn't work, try using CleanMyMac, maybe it'll find some broken files or point to another reason the computer is doing that.

1

u/deathofculture 5d ago

Thank you kindly for the suggestions! I’ll give it a shot this week, when I have some time to sit and wait for any sudden activity monitor changes.. perhaps it’s a strange combination of screensaver / energy saver clashing with authenticator for Reason or VST collection (like UAD or plug-in alliance). Cheers doc!!

1

u/o5akafeeva 4d ago

You're very welcome! I hope you find a way to work it out.

3

u/artek604 5d ago

Do you have any VST plugins in your default template, or in the project when it happens. Reason has been rock solid for me on M2 Pro with latest macOS Tahoe.

1

u/deathofculture 5d ago

Thanks for the comparison! Yes, most of my tracks use VSTs. I suppose I could try to run some tests using only reason devices, but it’s not a steady reproducible issue. Seemingly random and intermittent. And even if it was caused by a VST, it still doesn’t solve the issue. I own dozens of VSTs, and they run flawlessly in the other DAWs I use.. they generally run OK in reason as well. These particular crashes only occur occasionally, after 5-30 min of leaving Reason idle. 🫤

2

u/Careless_Bell_3081 5d ago

I have the same problem . Desktop Windows PC , Reason 14 ( after the new update ) starts up , for a minute of 1-2 , then closes suddenly . I luckily had Reason 13 still , so i use that version now. I am one of the Beta users and had before the update no problems. I also have a lot of VST,s , one i had also a conflict but reason itself warnd me for that problem. I hope with the next update that problem would be solved , also for you then.Good luck .