On Tuesday 09 August 2005 09:01, Thomas Renninger wrote: > We have to run powersave/kpowersave in valgrind before sending out > this time. > > Tracking this one down for 9.3 shortly before 10.0 is bad, we all have a > lot work to do?
This wasn't find, because nobody has this problem ever befor. Thats the point! If there where such problems we would have already get bugreports from the suse-laptop mailinglist or SUSE people. And I can't reproduce such memory leak with 9.3 and the 9.3 KPowersave version. The 30 MB of memory for KPowersave is full normal (discussed this with Adrian for shipping 9.3 version). This is shared memory (e.g. kdelibs etc). And after suspend to disk and resume all is normal for me and kpowersave consume the same shared memory as before, the same if I remove and plug in the ac adapter very often. > I have a feeling that this comes from scheme fetching code which should > have been elemintated from Holger ... I'm not sure about this, but *feel* don't help. Can you reproduce this? I can't see a memory leak or reproduce it. Cheer, Danny _______________________________________________ powersave-devel mailing list powersave-devel@forge.novell.com http://forge.novell.com/mailman/listinfo/powersave-devel
