[Webkit-unassigned] [Bug 67031] New: [chromium] ASSERTION FAILED: fontCache()->generation() == m_generation

[bugzilla-daemon at webkit.org]

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

           Summary: [chromium] ASSERTION FAILED: fontCache()->generation()
                    == m_generation
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: tonyg at chromium.org
                CC: mitz at webkit.org, pkasting at google.com,
                    jamesr at chromium.org


Jamesr noticed an ASSERT() fail on the mac bot:
ASSERTION FAILED: fontCache()->generation() == m_generation

build log:
http://build.chromium.org/p/chromium.webkit/builders/Webkit%20Mac10.6%20(CG)(dbg)/builds/202/steps/webkit_tests/logs/stdio

test was:
fast/css-generated-content/table-before-after-child-add.html

This ASSERT was added by mitz back in http://trac.webkit.org/changeset/35025 , so it is likely a problem w/ the chromium mac port rather than with the ASSERT itself. If this ASSERT is reached, it means that FontCache::invalidate() was called. One place we call that is in WebKit/chromium/src/WebFontCache.cpp::clear(). That gets called on low memory notification (from ChromeRenderProcessObserver::OnPurgeMemory()), and from the ASSERT it seems like that isn't safe to do. That was added way back in http://codereview.chromium.org/267021 .

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