Eero Tamminen <eero.tamminen@xxxxxxxxx> wrote:
Browser is serious resource hog. I've noticed that closing all windows sometimes doesn't help either. As I said earlier in this thread, I was trying to restart tablet-browser-daemon, but it didn't seem to help much. Ie. browserd released memory at first, but almost instantly started regaining "weight" to the point where it roughly was before restart.Anything large (say e.g. Python) waking up on the background will also be an
issue. You can check top (or strace) now and then to see whether something
does stuff on the background (even 1%) although you haven't specifically
requested it to do anything. If it is, please file a bug.
I've had a look at top over ssh connection and seen /usr/bin/pulseaudio --system --high-priority constantly floating around 1-3% of CPU time. Needless to say, device was lying on the desk next to me, doing nothing, not to mention anything media-related. I did killall media-player but that didn't help and pulseaudio was still working out.
However I've been listening to music earlier in the morning, took couple of calls etx. Then later in the day I've opened a camera to take a picture, which threw weird "Another application is using audio" message at me few times (while no app that I was aware of was running in the background). Strange.
I will look closer to this issue and file appropriate bugzilla entry when I get some concrete observations.
However I've been listening to music earlier in the morning, took couple of calls etx. Then later in the day I've opened a camera to take a picture, which threw weird "Another application is using audio" message at me few times (while no app that I was aware of was running in the background). Strange.
I will look closer to this issue and file appropriate bugzilla entry when I get some concrete observations.
Closing all browser windows occasionally is also a good idea. Www-pages &
Flashplayer can cause Browser to use huge amounts of memory & the dynamic
nature of that memory usage can make browser memory very fragmented. Certain
kind of pages (if I've understood correctly, with images animated from JS) can
still cause it to wake up in the background which causes browser to be swapped
in, and then out when the foreground app wants to do something (this issue is
even worse in upstream Mozilla/Fennec). We're trying to get that fixed for
next release, but it's possible that fix isn't ready in time for that one.
Again, I've set swappiness value to 60 yesterday, my N900 has 1d7h of uptime so far and I am monitoring its behaviour much closer than before. So far so good, but as I said initially - weird things start happening since approx. second/third full day of uptime.
--
Dawid 'evad' Lorenz * http://adl.pl
null://real men never use Gmail
_______________________________________________ maemo-users mailing list maemo-users@xxxxxxxxx https://lists.maemo.org/mailman/listinfo/maemo-users
