FR theme: Performance/memory issues

[larm]

numbers in MB:

startup 62 (with sequencer)
new modular 30
new sequencer 62
1 gpo added to modular env 87 (with sequencer)
1 gpo removed from modular env 87 (with sequencer)
1 gpo added to modular env 97 (with sequencer)
1 gpo removed from modular env 97 (with sequencer)
new modular 64
new sequencer 97
new modular 64
1 gpo added to modular env 74
1 sequencer added to modular env 107

sidenote:
Everytime gpo get's added the total amount is upped by 10 mb. That can be removed by creating a "new modular" setup, but as soon as the sequencer is added the memory usage of all the added+removed gpo's is back (some caching thing i guess)

--

startup 62 (with sequencer)
add audio track in seq 79
add audio track in seq 96
add drum track in seq 113
deleting audio track in seq 113
deleting drum track in seq 113
deleting sequencer 113
new modular 113
new sequencer 149 (uh-oh)
deleting all tracks inside sequencer 149
new sequencer 180 (?!? what did THAT memory usage come from??)
new sequencer 180
deleting all tracks inside sequencer 180
new sequencer 214 (hmm? just lost 40 mb to nothing...)
new sequencer 214
new sequencer 214
deleting midi track in seq 214
new sequencer 231 (lost 20 mb = one midi track)
new modular 199
new sequencer 232

---

So... what would cause this behaviour (no full release upon creating a new modular/new sequencer)?

Could it be some lost undo buffer (and it's now no longar available because of the new sequencer/modular (i.e. undo/redo buttons are disabled)) that prevents the memory from being released.

Only "borgen" knows..

hmm-hmm..

[Mighty Pea]

Yeah, i just compared it to xt1, and it's quite odd.
Xt1 is 3mb, xt2 63 O_o
Ofcourse, when adding a sequencer (to be fair), xt1 takes 7mb.

[Meffy]

I'd just like to take this opportunity to say, as an anthropomorphic skunk, that there is nothing at all wrong with ram-hog hybrids. [laputa] They're people too. [/laputa]

Though it's true I've always wondered what the parents saw in each other...

[farlukar]

​

ramhog.jpg

​
(or is that a hog-ram?)

[Meffy]

:-} Prototype gnu, not quite ugly enough. But it's open source!

[janka]

friday the 13th beta: Ram still is not released upon unloading vst-instruments.

[Holophonic]

Yea i noticed too, whats the point adding more features before the basic functions run smoothly and efficiently ?

[jens]

friday the 13th beta: Ram still is not released upon unloading vst-instruments.

and:

- still adding a new track increases the ram-usage by several mega-bytes

- deleting the same track doesn't free up the ram

[sc_a]

This RamZes!

[janka]

beta070421: still the same...
/Anders

[greneged]

Has anyone tried pointing out that prob to Jorgen directly? Maybe he ignores that thread because the title looks a bit "bashy" and is unaware how serious that all is.

To be frank, when that major issue does not get fixed soon, I'm off energyXT for a good while, if not forever. It bothered me in v.1.xx already when I noticed the RAM was not freed after deleting a track, but those worsened figures in the v.2betas really are giving me the creeps.

I really would like going on working with energyXT (even when switching to another host the plugin version could still be of use), but not when such fundamental problems persist without getting fixed.

Please Jorgen, do something about it.

[jorgen]

its high up on the list

cheers
jorgen

[greneged]

Good to hear, Jorgen.
I hope it's not sitting too deep in the code.

[jens]

its high up on the list

WOOHOO!!!

[acid1]

Memory leaks and bugs are a pain while programming. Its not fair to say "why add features when the basics don't work" because memory leaks is one of those things that most if not all programs suffer from time to time with after release.