Page 1 of 1
Live 6.0.1 - "Serious Program Error has occured".
Posted: Mon Oct 02, 2006 5:36 pm
by ilia
Was working on a set, got this message, which also said that Live would shut down after this. However, after I clicked ok, it just continued normally. I was able to save the set and restart Live. The only weird thing was that the set opened up as "dirty" right away - with a * next to it (not sure if this is related or not).
Posted: Mon Oct 02, 2006 6:30 pm
by Amaury
Hi Ilia,
If that happens again, and you can reckon specific conditions, see if you can reproduce the problem and let me know.
Kind regards,
Amaury
Posted: Mon Oct 02, 2006 6:38 pm
by camaro24gold
This is basically how it happened for me when I got this pop-up error. It said it would shut down after closing the pop-up.
I had too shut Reason down 1st (ReWired) and then was able to save the Live 6 set. Closed Live and reopened but any move I made within Live said the same pop-up error.
I hope when I reboot back to that partition of my drive Live 6 will not continue to do so.
the "A serious program error has occurred." message box lies
Posted: Tue Dec 19, 2006 11:22 am
by FrankH
I use Live 6.0.1 and am currently testing Live 6.0.2b10 on my Windows laptop computer, details are in my signature.
The "A serious program error has occurred." message box lies. It does not shut down Live after the message box is closed. A new message box is served over and over and over again. I get this one every day and i have to use Windows Task Manager to kill Live 6.
Reproducing this is not easy, it just happens when playing a song, there is no action related to this error.
edit: 6.0.2b20 is 6.0.2b10
Change the message
Posted: Fri Dec 22, 2006 3:38 pm
by FrankH
Live is not shut down after the message box is closed.
Can you change the text of the message box into:
Code: Select all
Go to Windows Task Manager and kill the Ableton Live Process.
Because this is the only true text phrase for this one.
By any chance are you running SampleTank when this happens?
Posted: Mon Jan 22, 2007 6:55 am
by dkcalifornia
I've noticed that only SampleTank 2.x projects do this to me.
Re: By any chance are you running SampleTank when this happe
Posted: Mon Jan 22, 2007 11:41 am
by FrankH
dkcalifornia wrote:I've noticed that only SampleTank 2.x projects do this to me.
I have this while using Ableton Live's own instruments.
Posted: Wed Mar 21, 2007 6:03 pm
by Hoitabuam
RAM -> 1 GB
Posted: Wed Mar 21, 2007 6:43 pm
by FrankH
Hoitabuam wrote:RAM -> 1 GB
CPU -> 2.8 GHz
serious
Posted: Thu Mar 22, 2007 10:11 am
by Hoitabuam
Hello all,
i could reproduce this behaviour by loading more instruments (by size) into live (sampler) than physical available RAM. Load 1,1 GB instruments on a machine with 1GB RAM produces this error (XP SP2).
Posted: Fri Mar 23, 2007 6:12 pm
by Aunt Acid
This happens to me when moving tracks in session view (not in arrangement view). Almost every time on large sets.
Posted: Wed Mar 28, 2007 4:09 pm
by milesahead
it happens to me when i try to render loops from reason,
so first it looked like a rewire problem.
but then again, it does the same thing when i render with vst-plugs,
or even with the live-own efx.
it does not crash then, but the "render to disc" screen will not disappear,
and the rendering does not happen.
curiously, sometimes no more rendering is possible,
and: sometimes after a few times, it`s rendering perfectly again.
i don`t try to save the whole set, because that way i am only making loops,
but it is strange and steals alot of time and nervs