On Wed, 2008-01-02 at 18:26 -0800, Jason Evans wrote:
quoted text > Joe Marcus Clarke wrote:
> > GNOME applications use a Python driven XML parser to generate help
> > document translations. The engine takes the English XML document and
> > applies translations to it. The tool, xml2po, is installed as part of
> > textproc/gnome-doc-utils. I'm currently working on porting GNOME 2.21,
> > and one of the Evolution help doc changes triggered a memory problem on
> > my test machine. Basically, with up to and including rev 1.154 of
> > malloc.c, I am able to generate the help file with no errors. With all
> > later revs including 1.160, the Python process balloons up to about 512
> > MB of memory, then dies.
> >=20
> > The only malloc config I've done is symlink Aj to /etc/malloc.conf. I'=
d
quoted text > > be happy to provide the file an exact command used, but it might be
> > easier to let me know if there's any debugging I could provide that
> > would help here.
>=20
> Revision 1.160 of malloc.c uses sbrk instead of mmap by default. The=20
> intent is to make data segment resource limits useful. So, there are=20
> two possible explanations I can think of for your problems. The first=20
> possibility is that there is still a bug in malloc that you're hitting.=20
> However, the other possibility is that the python program you're=20
> running really needs more than 512 MB of memory, and you're hitting the=20
> resource limit.
>=20
> It would be really helpful to me if you run your program with=20
> MALLOC_OPTIONS=3DdM and monitor memory usage. These flags cause mmap to=20
> be used instead of sbrk, and we can find out from that how much memory=20
> you really need. If peak memory usage is substantially different when=20
> using mmap versus sbrk, there's probably a malloc bug.
Memory climbed up to 976 MB SZ, 974 MB RSS MB with dM
-> /etc/malloc.conf. The file was eventually generated without error.
Again, with Aj -> /etc/malloc.conf, the python2.5 process operating on
the same file planed out at 504 MB SZ, 501 MB RSS.
quoted text >=20
> This latest round of malloc changes hasn't been much fun. Thanks for=20
> your help and patience.
No problem. Thanks for getting back to me.
Joe
--=20
Joe Marcus Clarke
FreeBSD GNOME Team ::
gnome@FreeBSD.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome