compiz eats memory

[Carl Karsten]

On Thu, Oct 27, 2011 at 8:23 AM, Carl Karsten <carl at personnelware.com> wrote:
> On Wed, Oct 26, 2011 at 7:57 PM, Carl Karsten <carl at personnelware.com> wrote:
>> install oneiric, run app, compiz eats memory, doesn't release it when
>> app is closed.
>> I  built compiz trunk, run app, no eat memory.
>>
>> app = dvswitch, it's from debian,
>> http://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=dvswitch/dvswitch.git;a=blob;f=src/mixer_window.cpp;h=961f57a89a70f71ae2dc6e0d24e8086bf26df378;hb=HEAD
>>
>> I am guessing this is not really enough for a bug report - what more can I do?
>>
>> Is ubuntu+1 installable, and have a different flavor of compiz?  I
>> would be happy to test that if it would help.
>>
>
> Tried +1, same thing.
>
> How do I run compiz under valgrind?

Top showed RES was 200m higher after 6 hours.  Not sure I see antthing
that looks like 200m.

juser at trist:~$ DISPLAY=:0 valgrind compiz --replace
...
==2250== HEAP SUMMARY:
==2250==     in use at exit: 1,021,622 bytes in 7,599 blocks
==2250==   total heap usage: 84,564,312 allocs, 84,556,713 frees,
24,168,799,342 bytes allocated
==2250==
==2250== LEAK SUMMARY:
==2250==    definitely lost: 988 bytes in 9 blocks
==2250==    indirectly lost: 3,057 bytes in 22 blocks
==2250==      possibly lost: 518,195 bytes in 3,778 blocks
==2250==    still reachable: 499,382 bytes in 3,790 blocks
==2250==         suppressed: 0 bytes in 0 blocks
==2250== Rerun with --leak-check=full to see details of leaked memory
==2250==
==2250== For counts of detected and suppressed errors, rerun with: -v
==2250== Use --track-origins=yes to see where uninitialised values come from
==2250== ERROR SUMMARY: 5255 errors from 66 contexts (suppressed: 22 from 6)


The app:
juser at trist:~$ DISPLAY=:0 valgrind dvswitch
....
==2316== HEAP SUMMARY:
==2316==     in use at exit: 46,217,916 bytes in 26,879 blocks
==2316==   total heap usage: 26,883,957 allocs, 26,857,078 frees,
2,573,439,024 bytes allocated
==2316==
==2316== LEAK SUMMARY:
==2316==    definitely lost: 30,720 bytes in 3,172 blocks
==2316==    indirectly lost: 37,584 bytes in 3,545 blocks
==2316==      possibly lost: 1,163,819 bytes in 9,174 blocks
==2316==    still reachable: 44,985,793 bytes in 10,988 blocks
==2316==         suppressed: 0 bytes in 0 blocks
==2316== Rerun with --leak-check=full to see details of leaked memory
==2316==
==2316== For counts of detected and suppressed errors, rerun with: -v
==2316== Use --track-origins=yes to see where uninitialised values come from
==2316== ERROR SUMMARY: 10000000 errors from 11 contexts (suppressed: 45 from 9)



-- 
Carl K