compiz team mailing list archive

[kayandus <bierfiltertje@xxxxxxxxxxx>]

Attached the full valgrind log, while running compiz for about 8 hours,
with options --leak-check=full --show-reachable=yes enabled. Most
interesting part is probably the last few lines of the log:

==17463== 314,222,480 bytes in 1,510,685 blocks are still reachable in loss record 7,754 of 7,755
==17463==    at 0x4C28F9F: malloc (vg_replace_malloc.c:236)
==17463==    by 0x4E7223E: _XEnq (in /usr/lib/x86_64-linux-gnu/libX11.so.6.3.0)
==17463==    by 0x4E6EE92: ??? (in /usr/lib/x86_64-linux-gnu/libX11.so.6.3.0)
==17463==    by 0x4E6FC6F: _XReply (in /usr/lib/x86_64-linux-gnu/libX11.so.6.3.0)
==17463==    by 0x11730A5A: ??? (in /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2)
==17463==    by 0x1172EE30: ??? (in /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2)
==17463==    by 0x11706F76: ??? (in /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2)
==17463==    by 0x114DB1A3: PrivateGLScreen::waitForVideoSync() (in /usr/lib/compiz/libopengl.so)
==17463==    by 0x114DB368: PrivateGLScreen::paintOutputs(std::list<CompOutput*, std::allocator<CompOutput*> >&, unsigned int, CompRegion const&) (in /usr/lib/compiz/libopengl.so)
==17463==    by 0x112A5F08: CompositeScreen::paint(std::list<CompOutput*, std::allocator<CompOutput*> >&, unsigned int) (in /usr/lib/compiz/libcomposite.so)
==17463==    by 0x112A777E: CompositeScreen::handlePaintTimeout() (in /usr/lib/compiz/libcomposite.so)
==17463==    by 0x424DBA: CompTimer::triggerCallback() (in /usr/bin/compiz)
==17463==
==17463== 315,954,288 bytes in 1,519,011 blocks are still reachable in loss record 7,755 of 7,755
==17463==    at 0x4C28B35: operator new(unsigned long) (vg_replace_malloc.c:261)
==17463==    by 0x436FF9: std::list<_XEvent, std::allocator<_XEvent> >::operator=(std::list<_XEvent, std::allocator<_XEvent> > const&) (in /usr/bin/compiz)
==17463==    by 0x431BF3: PrivateScreen::processEvents() (in /usr/bin/compiz)
==17463==    by 0x45EAD0: CompEventSource::callback() (in /usr/bin/compiz)
==17463==    by 0x623A9DE: Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) (in /usr/lib/libglibmm-2.4.so.1.3.0)
==17463==    by 0x66A6A5C: g_main_context_dispatch (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.3000.0)
==17463==    by 0x66A7257: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.3000.0)
==17463==    by 0x66A7791: g_main_loop_run (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.3000.0)
==17463==    by 0x42E8B5: CompScreen::eventLoop() (in /usr/bin/compiz)
==17463==    by 0x422279: main (in /usr/bin/compiz)
==17463==
==17463== LEAK SUMMARY:
==17463==    definitely lost: 420 bytes in 5 blocks
==17463==    indirectly lost: 240 bytes in 10 blocks
==17463==      possibly lost: 356,292 bytes in 3,767 blocks
==17463==    still reachable: 638,139,513 bytes in 3,076,735 blocks
==17463==         suppressed: 0 bytes in 0 blocks
==17463==
==17463== For counts of detected and suppressed errors, rerun with: -v
==17463== Use --track-origins=yes to see where uninitialised values come from
==17463== ERROR SUMMARY: 9591 errors from 1260 contexts (suppressed: 23 from 8)

Hope the bug will be fixed soon.

** Attachment added: "valgrind log of running compiz for 8 hours"
   https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/914773/+attachment/2802891/+files/compizleaks.log.bz2

-- 
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/914773

Title:
  Compiz memory leak and blank screen unable to login

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz-core/+bug/914773/+subscriptions