Thanks for all feedback.<br><br>After Christmas break I started with fresh 2008 installation and trying to install more and more applications and find suspect with combination of strace/htop.<br><br>thanks<br><br>Pit<br><br>
<div class="gmail_quote">On Dec 27, 2007 9:10 AM, Eero Tamminen <<a href="mailto:eero.tamminen@nokia.com">eero.tamminen@nokia.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><div><div></div><div class="Wj3C7c"><br>ext Brad Midgley wrote:<br>> A quick thing to check is running 'top' and looking for cpu bandits.<br>><br>> I had a 3rd part app gobbling up cpu due to a bug once; another time
<br>> an internal launcher app was going nuts and it turned out to be caused<br>> by an sdcard corruption problem.<br><br></div></div>A process waking up very often can also be a problem as it doesn't<br>allow hardware to sleep[1], but if it consumes very little CPU each
<br>time, you don't see it in "top". Strace can find those out, see:<br> <a href="http://maemo.org/development/tools/doc/strace" target="_blank">http://maemo.org/development/tools/doc/strace</a><br><br>
<br> - Eero<br><br>[1] For CPU, even a badly coded program shouldn't be active more often<br> than at several seconds intervals when it's not doing anything for<br> the user. Network access should happen *much* more infrequently
<br> (say at max 1/2 min interval even in badly coded program)<br><br>"<br> Want to be a bloat detective?<br> Pick a binary, any binary.<br> There, you found it!<br>"<br></blockquote></div><br><br clear="all">
<br>-- <br>Piotr<br>-------------------------------------