gui memory leak?
-
- KVRian
- Topic Starter
- 1159 posts since 26 Feb, 2006 from Fartland
+1Selfik wrote:+1 when?
Free MIDI plugins and other stuff:
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"
- KVRian
- 1134 posts since 4 May, 2008 from West London Depot
-
- KVRist
- 32 posts since 6 Aug, 2007 from france
hi lennard
any news on a fix for this ?Seems to be getting worse here after installing a quad core,Vista service pak 2.Changing latency on my card does nothing to avoid these huge cpu peaks.Just trying to eliminate some problems.
Still sounding great of course!
cheers careyj
any news on a fix for this ?Seems to be getting worse here after installing a quad core,Vista service pak 2.Changing latency on my card does nothing to avoid these huge cpu peaks.Just trying to eliminate some problems.
Still sounding great of course!
cheers careyj
- KVRAF
- 12522 posts since 21 Mar, 2008 from Hannover, Germany
Quite late but i havn't checked this bug so far. With Ableton Live 8.0.3 on Windows Vista 32-bit the Memory use of Live raises from 150 Mb to 220 MB after opening and closing Sylenth1 for 10 times. Doesn't happen with any other plugin. So also confirmed from my side, even if quite late.
Ingo Weidner
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1
-
- KVRer
- 9 posts since 12 Nov, 2008
Same problem here. Running Windows 7 Ultimate x64 with Ableton Live 8.0.4 and Sylenth 1 (x86) version 2.202.Lennard wrote:Happens here too, thanks for reporting! I'll look into it.
/sp0
-
- KVRist
- 440 posts since 13 Mar, 2002 from Munich / Bavaria / Germany
This code could close the memory leak. You must free the memory for the bitmaps, wenn the gui is deleted.
ADEditor::~ADEditor ()
{
if (frame)
{
close();
}
delete frame;
frame = 0;
// free some bitmaps
for (int i=0; i < IDB_CNT; i++)
{
if (hBM)
{
hBM->forget();
hBM = NULL;
}
}
}
- KVRAF
- 12522 posts since 21 Mar, 2008 from Hannover, Germany
Markus from Tone2.com wrote:This code could close the memory leak. You must free the memory for the bitmaps, wenn the gui is deleted.
ADEditor::~ADEditor ()
{
if (frame)
{
close();
}
delete frame;
frame = 0;
// free some bitmaps
for (int i=0; i < IDB_CNT; i++)
{
if (hBM)
{
hBM->forget();
hBM = NULL;
}
}
}
Nice hint, Markus. I hope Lennard will get it.
Ingo Weidner
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1
-
Echoes in the Attic Echoes in the Attic https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=180417
- KVRAF
- 12031 posts since 12 May, 2008
Why is he ignoring this?
I'm not sure about this philosophy of silence for a year and then all of a sudden "Surprise! Here's a great update!"
Seems a bit apple-ish...
I'm not sure about this philosophy of silence for a year and then all of a sudden "Surprise! Here's a great update!"
Seems a bit apple-ish...
-
- Banned
- 22457 posts since 5 Sep, 2001
[DELETED]
