451259 - "nye_bloat : trace_malloc_leaks" increased on 2008-08-12

Status: NEW

(SeaMonkey :: General, defect)

Description

[Serge Gautherie (:sgautherie)]

No reply to my 'Newsgroups: mozilla.dev.apps.seamonkey' post,
then filing this as a bug...

Comment 2

[Serge Gautherie (:sgautherie)]

Attachment: Graph

Comment 3

[Serge Gautherie (:sgautherie)]

Attachment: History data

The first drop to 730 KB: I can't explain.
Do you have a clue ?

Then, the 10 KB increase can be seen:
both from 730 to 740,
and from 850 to 860.

Andrew, could you try a run with the initial revisions ?
I'd like to know if it drops back to 850 or 860.

Comment 4

[Andrew Schultz]

The majority of trace-malloc leaks are not related to mozilla code and are due to leaks in the underlying libraries (gtk, glib, X) or gecko not doing the appropriate dance to get them to not leak.  Changes in trace-malloc can happen due to timing or just using the system libraries differently (not incorrectly).

You can see an analysis of the where the new memory is leaked from in http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1218527400.1218528297.16274.gz&fulltext=1
It's all libfontconfig and libpangocairo (system font / gfx libs).

Comment 5

[Serge Gautherie (:sgautherie)]

(In reply to comment #4)
> The majority of trace-malloc leaks are not related to mozilla code and are due
> to leaks in the underlying libraries (gtk, glib, X) or gecko not doing the
> appropriate dance to get them to not leak.

Ah !
Is this "WontFix" then, or should I look into moving this bug to a "Core" component ?

> You can see an analysis of the where the new memory is leaked from in
> http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1218527400.1218528297.16274.gz&fulltext=1
> It's all libfontconfig and libpangocairo (system font / gfx libs).

Linux nye Depend bloat on 2008/08/12 00:50:00
under "diffbloatdump.pl"