Summary: | ASSERTION FAILED: m_purgePreventCount in FontCache::getCachedFontData running svg/custom/animate-disallowed-use-element.svg | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Nikolas Zimmermann <zimmermann> | ||||
Component: | SVG | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | mitz, simon.fraser, thorton, webkit-bug-importer, zimmermann | ||||
Priority: | P2 | Keywords: | InRadar, MakingBotsRed | ||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
Nikolas Zimmermann
2012-03-13 09:08:48 PDT
*** Bug 82815 has been marked as a duplicate of this bug. *** I'll try to find a way to make this reproducible. This is causing crashes on the debug bots. I question why all the work is being done under willBeDestroyed() though. Looks like useless work (In reply to comment #3) > This is causing crashes on the debug bots. > > I question why all the work is being done under willBeDestroyed() though. Looks like useless work In case you missed my comment from the other bug report 82815, the work done there is absolutely needed when removing eg. tspan children dynamically from a text subtree - it's an optimization actually, to avoid rebuilding the whole text tree upon the next layout, if only a child got removed. Part of that logic lives in willBeDestroyed(). I think Tim knows what this is about as well. smfr, from the dupe:
> I think there's a documentBeingDestroyed that you could consult.
Created attachment 135182 [details]
patch
Landed in http://trac.webkit.org/changeset/112942 |