Application Memory problem since updating to Live 12

[Takeaction]

Same thing happening for me since beta. Whenever I load Ableton 12 the ram keeps growing higher on its own, even while doing nothing and no plugins loaded. My setup - M1 mac mini,8gb.

Copy of ableton 11 runs great though, please share a fix if you find one.

This describes exactly what’s happening to me too.

[Takeaction]

Same thing happening for me since beta. Whenever I load Ableton 12 the ram keeps growing higher on its own, even while doing nothing and no plugins loaded. My setup - M1 mac mini,8gb.

Copy of ableton 11 runs great though, please share a fix if you find one.

This describes exactly what’s happening to me too.

OK so after some more trial and error I've managed to figure out that the memory leak was something to do with the default project I had setup. After changing the default set I'm not having excessive RAM useage any more. Weird bug.

[[jur]]

Did you change anything in your new default template? (especially wrt to plugins)

[chasedestroy]

I'm having the same issue on a M3 MacBook and am being put in contact with ableton support, I'm in rehearsals with a reasonably large act and this is holding us back. Strangely, when I run this on a M2 MacStudio that is part of the same position on stage I don't have the RAM leak, and other sessions on the M3 MBP seem unaffected.

We are running 2 vst plugins and 1 max for live device, the plugin for the Acme HW Midiclock and the ERM Multiclock, and the Max for live device is a midi input quantize selector, its a set of buttons for changing the quantization resolution for incoming midi. ...hardly a heavyweight session, but it does contain a LOT of audio clips. The band plays a 3+ hour set.

Has anyone managed to edit an ableton 12 XML file to fake it being an 11 file? I've tried a few things and have corrupted a test session, that said I have seen it done (Ableton 10 to Ableton 9 a few years ago) with BBedit.

I'll report back when if I know more.

[chasedestroy]

Same thing happening for me since beta. Whenever I load Ableton 12 the ram keeps growing higher on its own, even while doing nothing and no plugins loaded. My setup - M1 mac mini,8gb.

Copy of ableton 11 runs great though, please share a fix if you find one.

This describes exactly what’s happening to me too.

OK so after some more trial and error I've managed to figure out that the memory leak was something to do with the default project I had setup. After changing the default set I'm not having excessive RAM useage any more. Weird bug.

What variable in the default setup did you change?

[JE Harvey]

I've had the same problem since updating to Live 12 - M1 Mac user here too

Have been in touch with Support and sent in a ton of Status and Crash reports and then, about a month ago, it suddenly resolved itself.

Until yesterday when the problem returned but it only returned when I had plugged in Push 2. When I unplug Push 2, it goes back to normal - plug Push 2 in and the ram just keeps growing higher.

I then worked out that I had removed Push 2 from my system about a month ago and that is why I thought the issue had been resolved.

I've been back in touch with Support but I'm wondering if we are all having the same problem i.e. Push

Jo

[djpinigai]

I've had the same problem since updating to Live 12 - M1 Mac user here too

Have been in touch with Support and sent in a ton of Status and Crash reports and then, about a month ago, it suddenly resolved itself.

Until yesterday when the problem returned but it only returned when I had plugged in Push 2. When I unplug Push 2, it goes back to normal - plug Push 2 in and the ram just keeps growing higher.

I then worked out that I had removed Push 2 from my system about a month ago and that is why I thought the issue had been resolved.

I've been back in touch with Support but I'm wondering if we are all having the same problem i.e. Push

Jo

Hey man, thanks for the input. I tried disconecting push 2, and it solved the ram problem. Looks like push2 is causing the bug. Thanks community, yet ableton team too lazy to check forums and fix stuff thats making me sad.

[vlptx]

I have the same problem since 12 beta.

And this is due (not with my Push2) to the fact that I open projects from previous versions, so a memory leak occurs on projects that were created in Ableton 8 and Ableton 9, I will not say about Ableton 10 for sure now. I tried to create a new project and a new template in version 12 and transfer the tracks of old projects there (from the browser on the left) but it did not help and the memory leak remained.

It's a huge fail guys!

Specs: MacBook Pro M1 Pro with 16GB, Sonoma 14.5

[[jur]]

I have the same problem since 12 beta.

And this is due (not with my Push2) to the fact that I open projects from previous versions, so a memory leak occurs on projects that were created in Ableton 8 and Ableton 9, I will not say about Ableton 10 for sure now. I tried to create a new project and a new template in version 12 and transfer the tracks of old projects there (from the browser on the left) but it did not help and the memory leak remained.

It's a huge fail guys!

Specs: MacBook Pro M1 Pro with 16GB, Sonoma 14.5

That's a very interesting observation. Did you already report to Support?

[vlptx]

I have the same problem since 12 beta.

And this is due (not with my Push2) to the fact that I open projects from previous versions, so a memory leak occurs on projects that were created in Ableton 8 and Ableton 9, I will not say about Ableton 10 for sure now. I tried to create a new project and a new template in version 12 and transfer the tracks of old projects there (from the browser on the left) but it did not help and the memory leak remained.

It's a huge fail guys!

Specs: MacBook Pro M1 Pro with 16GB, Sonoma 14.5

That's a very interesting observation. Did you already report to Support?

Of course, when this happened (and this was often the case) since Ableton 12 beta, I sent bug reports every time, but apparently no one paid attention to it or such information is not displayed in the generated bug reports, I don't know. I could send one of my projects in support, where it always happens, but I didn't get any feedback. Oh, and it happened again while I was writing this answer right now (96GB of memory leaked)

[vlptx]

I just sent to support a project in which it always happens, I really hope that the team will find the problem and fix it so that all other users no longer experience such a problem. I really hope I won't be ignored this time!

[[jur]]

I just sent to support a project in which it always happens, I really hope that the team will find the problem and fix it so that all other users no longer experience such a problem. I really hope I won't be ignored this time!

Thx! I'm forwarding on my end too.

[vlptx]

A funny end to the story of communication with support here. First of all, I want to say thank you to the support for letting us look further because after communicating with the support, we decide to change the DAW and look at other alternatives!

And now a detailed story:

Me - sent all possible crash reports and even a project in which this error (memory leaks) are reproduced, for Ableton 12.
Support - I don't see your account license for version 12, but only for version 11.
"explanation - here for the test I used Ableton 12.0.5 downloaded from the torrent to understand if this problem is global"

Me - ok, I have the same problem with Ableton 11, and I'm sending all the crash reports and the project from version 11.
Support - is silent for a long time and does not answer.

Me - sending crash reports this time from the licensed version of Ableton 12.0.10.
Support - sorry, I don't see a license for Ableton 12 version on your account.
“explanation - this time for the test I used the Ableton version 12.0.10 from the studio, activated offline at home"

It looks like it's time to move from Ableton to Reaper, I suppose!