Does not appear to affect Linux either - it seems this is MacOSX only so far. A regression range would be nice to have...
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: crash, pp, regression
gdb's backtrace for the testcase in comment 3 is kinda useless: (gdb) bt #0 0x00420044 in dyld_stub_fflush () #1 0x00420042 in dyld_stub_fflush () In an attempt to get a better backtrace, I modified the testcase to try adding one character to the string at a time until it crashed. I got this: (gdb) bt #0 0x9025ca97 in IteratorFindFontIDFromName () #1 0x6547736e in ?? () #2 0x4e5a5f3a in ?? () #3 0x00000000 in ?? () (gdb) info symbol IteratorFindFontIDFromName IteratorFindFontIDFromName in section LC_SEGMENT.__TEXT.__text of /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS There are no hits on Google for "IteratorFindFontIDFromName". Is this a bug in Apple code?
Regressed between 2007-01-05-06 and 2007-01-05-14 (there happened to be a nightly respin that day). There were several checkins to Mac font-choosing code during that period: bug 364785, bug 364832, and bug 365613.
The patch on bug 364785 is especially suspect because it plays with a buffer of size 1024.
The crash occurs during the first call to ATSUFindFontFromName in gfxQuartzFontCache::ResolveFontName: http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/gfx/thebes/src/gfxQuartzFontCache.mm&rev=1.12&mark=705-711#705
Whiteboard: [sg:critical] → [sg:critical] post-1.8-branch
Assignee: general → nobody
Component: DOM: Level 0 → GFX: Thebes
QA Contact: ian → thebes
Version: unspecified → Trunk
Created attachment 267592 [details] [diff] [review] fix Thank you for the testing. We should skip to resolve the long font name, but this patch cannot suppress same issues in future.
Assignee: nobody → masayuki
Status: NEW → ASSIGNED
Attachment #267592 - Flags: review?(vladimir)
Attachment #267592 - Flags: review?(vladimir) → review+
Status: ASSIGNED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.