Post the report log to try to help you.

Hi Overcoat - did you resolve the crash issue when closing Studio One? I'm using Studio One 2 pro on an imac 10.8.5 and the program never just shuts down - I always get "Studio One quit unexpectedly" I get an option to report the issue (to Apple) but I just hit ignore because it doesn't seem to cause any problems and it's been happening for a long time. I figure it might resolve itself in the next update - hopefully.
Regards... Steve

Having the same problems on two different Mac Pros running both Mavericks and Mountain Lion. It doesn't happen all of the time but I do get the dreaded "Studio One quit unexpectedly" message at least once a week.

Would like to add to this existing thread, in that I am almost always (say, 95% of the time) getting the "Studio One quit unexpectedly" alert at the tail end of doing a Quit on the app. Wouldn't that make it an EXPECTED quit? But seriously... it's the last thing I see on the screen. The rest of the app interface has already closed down. I don't lose anything, and nothing is corrupted when I reopen the song, but it's quite unnerving. Is it the general consensus that a third-party plug-in the culprit in these cases? I'm using some Arturia synths.

I have had issues since version 2 (since I have had S1, all versions of 2 and including V3).

I did post a bug report, got no answer and no fix. I often get a "Pure virtual function call" (C++) error message. S1 does not shutdown cleanly when this happens, I often have to use task manager to shut the instance down. Then, my recent songs list is changed to whatever it was the last time S1 shut down properly. S1 can do this (crashing on exit) sometimes when choosing "Close All", or just "Close" or when properly quitting (and not just closing projects)..

I just live with it, as, like I said, support weren't interested in this problem. I even sent crash dump files etc.

I was wondering if it was related to a plugin, or was a VST/VSTi issue perhaps?

Justin

[edit] - I am running Windows 7 SP1, 64bit.

I'm thinking that is must be a misbehaving plug-in. I should try to create some songs that have no AU or VST instrument tracks, and see if this still happens. Betcha it won't...

This happens often for me with no other ill effects (v3.0 - win7Sp1 - 64bit)

Plug ins vary and sometimes with none at all at the start of a song

Yes, I have to say it happens with so many if not all of my projects that, if it is a plugin or virtual instrument, it is probably more than one causing the problem. It could be possibly a dozen or more. So is the problem with the plugin, or studio one? I mean, VST is a standard, and you'd think that such standards are adhered to.. I know Reaper had a plugin firewall, so the issue surely could be handled by studio one, assuming that it is a plugin or many plugins to blame. Given that so many of my projects do this, and given the fact that you all probably don't have close to the same instrument and plugin set I have, then it is better solved at the DAW level?

One observation: the last time S1 (Version 3 Pro) crashed on me, I reopened the exact same song, and did nothing to require a re-save. I then closed S1 and it didn't crash. That tells me that it is a S1 issue.. I mean, the exact same song, in the exact same saved state, crashes one time but not another. Identical plugins used etc..

It just crashed again on me just now..

I had saved a song I was working on. Then I chose "Close All" and I got the usual "Pure Function call" C++ error.. then I got the Windows error "Studio One has encountered an error and needs to close"..

Reopened the same song that I had open when the close made Studio one crash, and the play marker was halfway through (not at the start as it usually is) and the click track (which definitely was NOT on when I saved it before) was on..

This is clearly a Studio One issue. Why would a plugin of mine cause the click track to be reactivated due to a crash?

Does Studio One staff read these threads? This bug has been present since V2.X.X and to be honest it is unnerving, I sometimes think "Ok, how can I manage to close a song without it crashing?"

No, I have been told that PreSonus staff do not frequent these user support forums. If we believe we have found a bug that needs addressing, I believe we have to submit a support ticket at http://support.presonus.com/requests/new

jsljustin wroteIt just crashed again on me just now..

I had saved a song I was working on. Then I chose "Close All" and I got the usual "Pure Function call" C++ error.. then I got the Windows error "Studio One has encountered an error and needs to close"..

This is clearly a Studio One issue. Why would a plugin of mine cause the click track to be reactivated due to a crash?

No... it's not clearly a Studio One issue.
I have nearly the same PC as you but with Win8.1 and I've not had this issue. I've opened v3 ~30 times with no problems.

In the past, I did have this occur a couple times with v2 on an older laptop... but... over a period of 2 years.

Could it be the block/sample size setting in your Audio Interface?
What's your CPU meter doing?
More intensive plugins and multiple instances of them will increase the CPU meter. A PC can only run so many items before something bad happens.

scottyo7 wroteNo... it's not clearly a Studio One issue.
I have nearly the same PC as you but with Win8.1 and I've not had this issue. I've opened v3 ~30 times with no problems.

I have no problems opening Studio One, it is crashing on exiting.
The error I get is a C++ runtime pure virtual function call. The faulting module for me is reported as the Presonus Cross platform module, which might be why I am getting the crash on exit on Windows 7, but you are not getting it on Windows 8?

I have seen this issue with 3.1 on Windows 10.
Usually all that is needed is to install the latest c++ redistribute for 32bit or 64bit depending on your OS .

Would be good if devs / tech sort this or make a faq on how to fix it.

I had a client with the "Crash on closing" errors. He had set up (connected) a midi keyboard, then unplugged it later (because it wasn't being used anymore.) As long as he had it unplugged, it crashed. (It took him a long time to figure out that it didn't crash when plugged in, since he rarely used it...)

Once he removed that keyboard from S1, it closed cleanly instead of crashing.

Another had an external hard drive that had a USB cable that was too long and going through a hub of some sort.

The drive worked most of the time, but once the drive was directly connected with a shorter USB cable, it stopped crashing during the close sequence.

Lots of moving parts, and these may NOT relate to your issues. In both of the cases above, it appeared to be an S1 issue, but really it was related to how the items were connected or not.

S1 shouldn't crash if a keyboard or other hardware device is no longer connected, but in the cases above it wasn't losing any data, so I suspect that's considered a lower priority issue.

You guys do realise that a pure virtual function call error occurs when a base class incorrectly, or wrongly calls a method or a function of that derived class, and in this case, from the destructor?

The destructor gets called when S1 is closed, or attempted to close. Irrespective of what you may think can cause or fix this issue, the fact remains that the code from within the destructor needs to be fixed. This, again is the responsibility of whoever is responsible for maintaining and checking the code, in this case the code that is written within the destructor of studio one's main application.

crash on exit here. every song, every project. OSX 10.5.5 and current S1 Pro

Support was no help

shanabit wrotecrash on exit here. every song, every project. OSX 10.5.5 and current S1 Pro

Ditto .... OSX Yosemite S1 pro v2.65 and now S1 pro v3.1
Doesn't seem to affect anything saved - just annoying. The developers must be aware of the problem as it's been ongoing for ages now but every update/upgrade has failed to fix the issue!
Maybe it relates to a problem outwith of S1 but it would be nice to have an official explanation... Eh Presonus?

Regards.....

This crash on shutdown issue has plagued me for years now.

At this point I'm on the latest version of 3, OSX 10.10.5. Crashes are with or without an interface attached, and regardless of plugins used.