The Not Enough Memory Issue

[concrete_cow]

Hi Michael,

I'm using the latest beta version 8.10 on leopard. I've got about 10 songs, some with 60-100 warp markers in them and across 8 clip. I also have an 5 loopers and an APC which is midimapped up to the eyeballs. I tend to get this problem after saving the set between 8-15 times.

I've read statements on the forums suggesting that that there is a problem with the new warping function on live 8, is this the case and if so is there a fix in the pipeline? I've read about live 7 users having the same memory problem as well however, so maybe this isn't new warping related?

Thanks,
Sunil

[samplehead]

I suspect the problem is in fact a memory leak in saving the project. I can open a project, do nothing to it, except keep saving it over and over and eventually it will say "not enough memory to save"

[[mid]]

Hey Sunil,

please send a zipped .als file of your problematic set to support. make sure to include your computer specs and the description of the problem.
Then we'll investigate from there.

Thanks,
Michael
Ableton HQ

[friend_kami]

i get these errors aswell, sometimes with a near empty set.
the culprit for me?

looper. i only get these problems when i have looper in the sets.
too bad since looper and group tracks was the number one reason to upgrade.
ironic.

[samplehead]

Yep, Loopers use RAM based audio buffers I think. I have 8 Loopers in my set.

Other weird stuff happens, sometimes some audio will play from a Looper that was CLEARED out some takes ago!

[friend_kami]

Yep, Loopers use RAM based audio buffers I think. I have 8 Loopers in my set.

Other weird stuff happens, sometimes some audio will play from a Looper that was CLEARED out some takes ago!

yeah, that too.
supposed to be one of the big big things with the upgrade and its useless.
way to go. alpha, anyone?

[ludollorca]

I'm not using looper or beat repeat, and i get this Not enough memory thing.
Basically, here's what i have : an ableton live 8 project, let's call it A.
I'm opening A. So far, so well. I'm saving a new project of A, called A2.
If i'm opening A2 and saving it again under a new project called A3, no problem.
If i'm opening A2, PLAYING IT (simply playing, not even changing anything in the track), and saving it under a new project called A3, next time i'm gonna try to open A3, i'll get this 'not enough memory' message. And that's it. No clips on screen, nothing.
I tried to get rid of the samples i use in the project A2 or A3, to see if it was a audio clip / sample-related problem, and i still get the same error.
I tried loading the project with no VST (just changing the name of the vst folder, so that ableton live won't access it), and still the same.
Therefore, it is something INSIDE the project that make this error occur, it's not because of some audio, clip or vst.

[ludollorca]

and i must add that it doesnt happen with every project. with some, yes, and i can't find a way to fix it. with some, everythings' ok.
and oh, after this crash and quitting ableton live, i can 'feel' windows explorer is getting a lil bit laggy by navigating in folders, even though the ableton live 8 instance isnt appearing anymore in windows' task manager.
hope it helps.
(live 8.0.4, windows XP sp2 / rme multiface / p5b deluxe motherboard)

[nowtime]

Damn - I just got it. This is a serious and unacceptable error.

I was just putting the feather in my cap, my ultra-mega-live set. Adding song 8 to a set of 150 scenes, for a total of 160 scenes. That's when it happened.

My comp is showing 3.5 to 3.9 gig of ram being used. This is new. Live 7 never went over 2.9-3.1.

And the sucker crashed me beyond recovery.

What now?

[[mid]]

@ ludollorca and @ nowtime

Do you experience the problem also after rebooting Live after you had loaded a RAM hungry set?

Additionally try if this happens with the actual BETA which you can find here:
http://forum.ableton.com/viewforum.php?f=1

Please send the sets (.als file only) with which you can provoke the error. Send them to our support address and add a description of the problem. Make sure to include your complete computer specs.

Thanks!

Best,
Michael
Ableton HQ

[eisnein]

having similar problem. just started this past weekend.

Live 8.0.1
os x 10.5.4


posting to follow thread.

[benjarwar]

I've just started using Live 8 and I'm having this issue.

Started today, it happens consistently after running Live for a while (maybe > 1 hour) and saving often.

I'm using no clips and no samples, but I do have three Loopers going, plus a lot of keystroke and midi mappings. I'm sync'd to a Roland FC-300 MIDI foot controller going through Midi Translator to control the looping functions. Also running Reason slaved to Live 8 (as primary beat maker).

I have plenty of memory (2GB, running at approx. 60% memory idle). Live 8's CPU Load Meter tops at 31%.

MacBook Pro 10.5.8
Live 8.0.4

[whenchyiv]

I've just started using Live 8 and I'm having this issue.

Started today, it happens consistently after running Live for a while (maybe > 1 hour) and saving often.

I'm using no clips and no samples, but I do have three Loopers going, plus a lot of keystroke and midi mappings. I'm sync'd to a Roland FC-300 MIDI foot controller going through Midi Translator to control the looping functions. Also running Reason slaved to Live 8 (as primary beat maker).

I have plenty of memory (2GB, running at approx. 60% memory idle). Live 8's CPU Load Meter tops at 31%.

MacBook Pro 10.5.8
Live 8.0.4

I just ran into it as well. Live 8.0.5, no clips in RAM, 15 GB free on my main drive, and 2 GB of RAM. Ableton rules, I feel so confident using it Live.

[saffron]

Do all versions of live use 4gb of ram on mac?
Or are you just referring to live 8?

[koyas]

Same annoying "not enough memory" problem here on Live 8.0.8.
Using no looper, only VSTi.
Live is using around 1.2gb on task manager.
Should I send .als file?