Andrew Ash wrote:
> Also, can you reproduce it on Edgy?
Yes. I just looked through the mem maps of a running xmms process that
is listed as taking 114 MB of Virtual Memory. I found several offending
libs:
/usr/lib/libdrm.so.2.0.0 has a 20 bit alignment requirement in its
program header according to objdump -x. This causes a 1 MB mapping to
be made even though the entire file size is only 31 KB.
/usr/lib/libvorbis.so.0.3.1 is another offender causing a 1 MB mapping
with a total file size of only 172 KB.
/usr/lib/libXfixes.so.3.1.0 is using a meg mapping for a 21 kb lib
/usr/lib/libXi.so.6.0.0 uses a meg for only 33k
/usr/lib/libz.so.1.2.3 wastes an extra meg for an 89 KB lib
You get the idea, there are a lot of them like this. If you see a
"2**20" in the objdump of the file, it has this problem.
Andrew Ash wrote:
> Also, can you reproduce it on Edgy?
Yes. I just looked through the mem maps of a running xmms process that
is listed as taking 114 MB of Virtual Memory. I found several offending
libs:
/usr/lib/ libdrm. so.2.0. 0 has a 20 bit alignment requirement in its
program header according to objdump -x. This causes a 1 MB mapping to
be made even though the entire file size is only 31 KB.
/usr/lib/ libvorbis. so.0.3. 1 is another offender causing a 1 MB mapping
with a total file size of only 172 KB.
/usr/lib/ libXfixes. so.3.1. 0 is using a meg mapping for a 21 kb lib libXi.so. 6.0.0 uses a meg for only 33k libz.so. 1.2.3 wastes an extra meg for an 89 KB lib
/usr/lib/
/usr/lib/
You get the idea, there are a lot of them like this. If you see a
"2**20" in the objdump of the file, it has this problem.