[Webkit-unassigned] [Bug 41169] New: Safari crashes Windows when opening a page with @font-face rule
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Jun 24 11:05:53 PDT 2010
https://bugs.webkit.org/show_bug.cgi?id=41169
Summary: Safari crashes Windows when opening a page with
@font-face rule
Product: WebKit
Version: 528+ (Nightly build)
Platform: PC
OS/Version: Windows XP
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: CSS
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: robin.cao at torchmobile.com.cn
Created an attachment (id=59680)
--> (https://bugs.webkit.org/attachment.cgi?id=59680)
a page containing @font-face rule
Opening the attached page (containing @font-face rule) in latest Safari will crash Windows every time. My OS is Windows XP.
I also tried with WebKit ToT builds, the result is same. But the page works well with Chrome for Windows.
A simple investigation reveals it may relate to GDI font API. The following is the call stack before Windows crashes.
DWORD GetGlyphOutline(HDC, UINT, UINT, LPGLYPHMETRICS, DWORD cbBuffer, LPVOID, const MAT2 *);
WebCore::SimpleFontData::initGDIFont()
WebCore::SimpleFontData::platformInit()
WebCore::SimpleFontData::SimpleFontData(const WebCore::FontPlatformData &, bool, bool, WebCore::SVGFontData *)
WebCore::CSSFontFaceSource::getFontData(const WebCore::FontDescription &, bool, bool, WebCore::CSSFontSelector *)
WebCore::CSSFontFace::getFontData(const WebCore::FontDescription &, bool, bool)
WebCore::CSSSegmentedFontFace::getFontData(const WebCore::FontDescription &)
WebCore::CSSFontSelector::getFontData(const WebCore::FontDescription &, const WebCore::AtomicString &)
WebCore::FontCache::getFontData(const WebCore::Font &, int &, WebCore::FontSelector *)
WebCore::FontFallbackList::fontDataAt(const WebCore::Font *, unsigned int)
WebCore::FontFallbackList::primaryFontData(const WebCore::Font *)
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list