[Webkit-unassigned] [Bug 43516] REGRESSION: Huge number of memory leaks after enabling MathML

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=43516





--- Comment #5 from Beth Dakin <bdakin at apple.com>  2010-08-05 10:06:14 PST ---
(In reply to comment #1)
> OK.  I've asked before about trying to detect leaks.  Pardon my ignorance, but what exactly are we looking at in these DumpRenderTree*-leaks.txt files?  How do I understand what they are saying?
> 
> I have a hunch this all has to do with the anonymous render objects created by the MathML rendering code.  RenderMathMLOperator creates quite a few of these and will re-create the glyphs stack (and the anonymous objects) every time layout is called.

Seems like you figured this out on your own, but in general, in case you are still curious…

You can get the leaks on your own machine if you want rather than looking at the leaks bot logs by running "run-webkit-tests --leaks". In this case since we know we want to focus on MathML leaks, looking at "run-webkit-tests --leaks mathml/" works even better.

The spew is a backwards backtrace to the point in the stack where memory that has been leaked was first allocated. In this case, it is hard to look through the logs because it looks like we are leaking RenderObjects, so there are some (very helpful) backtraces that show a RenderObject being leaked…but then since the RenderObject is leaked, everything the RenderObject owns is also leaked, so we get a bunch of much-less-helpfull stacktraces showing, for example, a HashMap that has leaked from the Font class. This is less helpful because it is not directly the problem.

I hope that helps.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.