[RESOLVED] Memleak
[RESOLVED] Memleak
happened during a gui init after hours of use
which is why its probably a memleak
was latest version
which is why its probably a memleak
was latest version
Re: Memleak
And the original bug report was:
It could be a memleak...or something else. I'll look into it.
So the way I understand the bug you mean the Synth freezes when openening the GUI after having it running, opening closing the gui etc, for several hours ?!MadGonzo wrote:inf loop during gui load, must be memleak
worked a couple of hours on an instrument (without saving )
It could be a memleak...or something else. I'll look into it.
Re: Memleak
happened again
thankfully i saved, and ill try to figure out which of the sounds actually crash
though it did happen on a gui init as usual
i just cant remember which of them
thankfully i saved, and ill try to figure out which of the sounds actually crash
though it did happen on a gui init as usual
i just cant remember which of them
Re: Memleak
Thanks for the follow-up!
Let me know if you find any more clues.
Perhaps you can send me the patch?, although I don't know if this is related to the problem.
Let me know if you find any more clues.
Perhaps you can send me the patch?, although I don't know if this is related to the problem.
Re: Memleak
another crash, though this time i know what caused it
frequent add/delete of LFO (connected to an envelope<->Amplitude) connected to the Tune of an Osc2
in other words frequent adding and removal of 2 modulators, last time i removed the LFO first, which was between Tune and an Envelope
again Envelope was modulating the strength of the LFOing
frequent add/delete of LFO (connected to an envelope<->Amplitude) connected to the Tune of an Osc2
in other words frequent adding and removal of 2 modulators, last time i removed the LFO first, which was between Tune and an Envelope
again Envelope was modulating the strength of the LFOing
Re: Memleak
I still havn't managed to reproduce this bug during bughunting....
Do you have any further clues with respect to this bug???
I've tried to create an Envelope->LFO(Amount)->Osc2 (Tune) patch like shown below, and then delete and add (and connect again) the LFO several times...I've also tried deleting both LFO and Envelope and adding again. No crashes yet.
Does my setup match yours ?
Please, I need more help in order to fix this in v1.07.
Do you have any further clues with respect to this bug???
I've tried to create an Envelope->LFO(Amount)->Osc2 (Tune) patch like shown below, and then delete and add (and connect again) the LFO several times...I've also tried deleting both LFO and Envelope and adding again. No crashes yet.
Does my setup match yours ?
Please, I need more help in order to fix this in v1.07.
Re: Memleak
that looks about right
although my instruments usually have alot more stuff
unison, phaser, reverb, delay
btw you should try experimenting with different:
1. polyphony
2. bipolar settings on all the modulators
3. add unison
4. try Trigger on main generator and see if things change
5. the crash happened when i removed the LFO (breaking 2 links)
but i havent had any real crash issues lately.. unless i can reproduce this problem again i dont think its "common enough" to be worth looking for
although my instruments usually have alot more stuff
unison, phaser, reverb, delay
btw you should try experimenting with different:
1. polyphony
2. bipolar settings on all the modulators
3. add unison
4. try Trigger on main generator and see if things change
5. the crash happened when i removed the LFO (breaking 2 links)
but i havent had any real crash issues lately.. unless i can reproduce this problem again i dont think its "common enough" to be worth looking for
Re: Memleak
ok, thanks for the swift reply.
I will try your suggestions.
I will try your suggestions.
Re: Memleak
i made it crash again, this time working with the same setup like this:
osc2 with hardsync, unison, moog filter, amp, notepitch (legato), phaser, delay
osc2 -> LFO -> envelope
removed envelope, all ok
removed LFO, synth crash
was still playing at the time i think
managed to save a partial .fst which obviously is of no use to anyone
osc2 with hardsync, unison, moog filter, amp, notepitch (legato), phaser, delay
osc2 -> LFO -> envelope
removed envelope, all ok
removed LFO, synth crash
was still playing at the time i think
managed to save a partial .fst which obviously is of no use to anyone
Re: Memleak
I've created a similar patch to the one you describe...and had it running for ages, while deleting, recreating the lfo/env modules. but no crash yet.
....if possible please send me the patch.
....if possible please send me the patch.
Re: Memleak
its the case where you restar the app each time
instead you should set it up, and reload the patch a gazillion times (or a project file)
FL was corrupted, not soon after i made it FL reported the FLP as being invalid, which it wasnt
i think the synth crashed before, because i had lots of other stuff in the project as well
when theres only 1 synth, it will take some reapplied leakage to make things break
http://commandante.fwsnet.net/192/frewferfre.zip
thats the near-death flp, which probably is a-ok..
or
http://commandante.fwsnet.net/192/crashy.fxp
instead you should set it up, and reload the patch a gazillion times (or a project file)
FL was corrupted, not soon after i made it FL reported the FLP as being invalid, which it wasnt
i think the synth crashed before, because i had lots of other stuff in the project as well
when theres only 1 synth, it will take some reapplied leakage to make things break
http://commandante.fwsnet.net/192/frewferfre.zip
thats the near-death flp, which probably is a-ok..
or
http://commandante.fwsnet.net/192/crashy.fxp
Re: Memleak
I got the synth to freeze after loading "crashy.fxp" several times.
So, by "crash" do you mean that the plugin freezes (making the host not responding) or that the host app exits with an exception error ?
Maybe its two different bugs.
So, by "crash" do you mean that the plugin freezes (making the host not responding) or that the host app exits with an exception error ?
Maybe its two different bugs.
Re: Memleak
yea, thats what i thought right after posting yesterday..
its more another memleak casued by unload (/load)..
you know, its a big monster youve been making here
i just tried Zebra2 demo today, and it was a big ass disappointment
i didnt like most of the presets on it, but i was borderline depressed by the UI
their best preset vs. a random from my bank wasnt even close (using same external fx to lushify sound )
anyways, as i said before its not a super-important bug as its only happened maybe 3 times so far
and i use the synth ALOT...
which is why i hound you for this and that, and even some more of some other stuff
btw i noticed Zebra2 had the same "sound"/aliasing as you do.. so it's probably khz related
care to comment on the other post? i had some questions
its more another memleak casued by unload (/load)..
you know, its a big monster youve been making here
i just tried Zebra2 demo today, and it was a big ass disappointment
i didnt like most of the presets on it, but i was borderline depressed by the UI
their best preset vs. a random from my bank wasnt even close (using same external fx to lushify sound )
anyways, as i said before its not a super-important bug as its only happened maybe 3 times so far
and i use the synth ALOT...
which is why i hound you for this and that, and even some more of some other stuff
btw i noticed Zebra2 had the same "sound"/aliasing as you do.. so it's probably khz related
care to comment on the other post? i had some questions
Re: Memleak
I may have fixed this issue now.
Deleting a module within a unison/polyphonic patch could occasionally cause an access violation => crash.... I'll have to test it some more.
Deleting a module within a unison/polyphonic patch could occasionally cause an access violation => crash.... I'll have to test it some more.