maemo.org Bugzilla – Bug 3704
Browserd Leaks Huge Chunks of Memory When Killed
Last modified: 2008-09-22 14:33:28 UTC
You need to
before you can comment on or make changes to this bug.
Latest Diablo release.
STEPS TO REPRODUCE THE PROBLEM:
Start MicroB, load some problematic pages (see
https://bugs.maemo.org/show_bug.cgi?id=3703 for example), kill browserd
manually several times, quit MicroB.
The available memory amount (as reported by CPU load applet) should be the same
as before MicroB has been started.
The memory amount gradually decreases and very soon the tablet starts running
out of memory and slows to a crawl.
The problem appears to be related to browserd allocating large chunks of shared
memory which (due to Linux shared memory implementation) continue to linger
after browserd is unexpectantly killed.
i think you probably want to install:
sp-memusage - memory usage reporting tool
sp-smaps-measure - /proc/pid/smaps snapshot generator
and provide detailed output showing which app is actually spending the memory.
when a process dies, it's dead<period> it can't leak memory, unless the kernel
or x server leak it.
if the xserver leaks it, that's usually a bug in the xserver.
if the kernel leaks it, then in one case that's a design both in Linux, and
it's not our fault.
As no useful information was provided (CPU applet doesn't show
the amount of the free system memory accurately enough to be useful
for this bug, there was no info how the supposed browser leakage
was measured etc) and this wasn't reproducible, I would mark this
sp-memusage package can be installed from the tools repository according
to the instructions here:
It's mem-monitor-smaps script can be used to report device free
memory and process memory usage accurately enough.
Data about shared memory segments (and other system resource) usage changes
can be logged with the tools&scripts in the sp-endurance package.
> (as reported by CPU load applet)
This has (small) memory leaks at least in the process memory usage list.
Closing as INVALID. Please reopen or file a new (clean) ticket when providing
more explicit information as described by Eero.