[Webkit-unassigned] [Bug 26484] New: ASSERT_NOT_REACHED reached in FontCacheChromiumWin.cpp:291

[bugzilla-daemon at webkit.org]

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

           Summary: ASSERT_NOT_REACHED reached in
                    FontCacheChromiumWin.cpp:291
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Windows XP
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: Platform
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: nsylvain at chromium.org
                CC: ojan at chromium.org


In the font code for chromium, we try to load font, and if it fails because of
the sandbox, we ask the browser process to try to load it by calling
ensureFontLoaded. If it still fails after ensureFontLoaded, we hit a
ASSERT_NOT_REACHED.

This case happens once in a while during browser shutdown. The browser will
queue a message to the renderer to shutdown, and will then stop answering sync
messages from the renderer. If the renderer is still loading a page during this
time, it might try to call the browser process to ask to load a font. The
browser process will ignore the request, and the font will fail to load, even
after the second try.

This is unfortunate, but there is no real risk here, since the renderer will be
going away as soon as it processes another message.

My proposal is to change  FontCacheChromiumWin.cpp:291
from:
ASSERT_NOT_REACHED();
to: 
LOG_ERROR("Unable to get the font unicode range after second attempt");


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