I just wanted to say that there is seems to be no evidence of memory usage growing. I am not sure how a vector could be growing without memory growing.I guess it could be growing in a pre-allocated space, though. But another update... the work pc shows compiz now at 47% since Fri afternoon. I ran another perf top -p compizPID on it. I think my previous output was truncated, so here is another output with more info in the line. I guess this is some kind of a trace. Maybe it will help. Finally, I will have to restart compiz on my work pc tomorrow. Is there any more info anyone would like to gather while we have an opportunity to get to this bug ? PerfTop: 372 irqs/sec kernel: 1.9% exact: 0.0% [1000Hz cycles], (target_pid: 1898) --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- samples pcnt function DSO _______ _____ __________________________________________________________________________________________________________________________________________ _______________________________ 5419.00 97.0% __gnu_cxx::__normal_iterator > > std::__find<__gnu_cxx::__normal_iterator > >, int>(__gnu_cxx::__normal_iterator > >, __gnu_cxx::__normal_iterator > >, int const&, std::random_access_iterator_tag) libnux-graphics-1.0.so.0.1600.0 Thank you for all input and work ! Michael Knap http://michaelknap.net Instructor and Researcher Mathematics and Controls Engineering Center of Excellence in Information Systems Tennessee State University On Sun, Jan 29, 2012 at 9:34 PM, Daniel van Vugt