479771 - Crash [@ libobjc.A.dylib][@ gfxAtsuiFont::GetCharWidth] when browsing StackOverflow.com

Status: RESOLVED INVALID

(Core :: Graphics, defect)

Description

[Gordon Thompson]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.6) Gecko/2009011912 Firefox/3.0.6
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.6) Gecko/2009011912 Firefox/3.0.6

When browsing through Stackoverflow.com, Firefox crashes when I click on certain links. There doesn't seem to be a pattern to the links. Sometimes it's down to expanding comments othertimes opening a question causes the crash.

This is the latest public build

Theme : Camifox 1.4
Extensions : Adblock Plus 1.0.1, CustomizeGoogle 0.76, Fast Dial 2.22b, FireGestures 1.1.6, Foxmarks 2.7.2 and Undo Closed Tabs Button 3.0.3


Reproducible: Sometimes

Steps to Reproduce:
1.Open stackoverflow.com
2.Browse through links, expanding comments when possible
3.
Actual Results:  
Browser quits

Expected Results:  
Firefox shouldn't crash, the worst it should do is to popup and error message

Comment 1

[Gordon Thompson]

http://crash-stats.mozilla.com/report/index/7cf89db7-720b-41eb-9dae-9426b2090223

That is the crash-report

Comment 2

[timeless]

reporter: could you try to get an apple crash report and *attach it* - click "Add an attachment" - without that, we don't know much about the QD/ATS frames.

Signature	libobjc.A.dylib@0x15688
UUID	7cf89db7-720b-41eb-9dae-9426b2090223
Time	2009-02-23 00:00:00
Uptime	61762
Last Crash	61765 seconds before submission
Product	Firefox
Version	3.0.6
Build ID	2009011912
Branch	1.9
OS	Mac OS X
OS Version	10.5.6 9G55
CPU	x86
CPU Info	GenuineIntel family 6 model 7 stepping 6
Crash Reason	EXC_BAD_ACCESS / KERN_INVALID_ADDRESS
Crash Address	0x95271688

0 	libobjc.A.dylib 	libobjc.A.dylib@0x15688 	
1 	ATS 	ATS@0x18244 	
2 	QD 	QD@0x81ce 	
3 	QD 	QD@0x1e0e8 	
4 	QD 	QD@0x1debc 	
5 	QD 	QD@0x1d612 	
6 	QD 	QD@0x2f28e 	
7 	QD 	QD@0x946d4 	
8 	QD 	QD@0x8dbc6 	
9 	XUL 	gfxAtsuiFont::GetCharWidth 	mozilla/gfx/thebes/src/gfxAtsuiFonts.cpp:339
10 	XUL 	gfxAtsuiFont::InitMetrics 	mozilla/gfx/thebes/src/gfxAtsuiFonts.cpp:282
11 	XUL 	gfxAtsuiFont::gfxAtsuiFont 	mozilla/gfx/thebes/src/gfxAtsuiFonts.cpp:117
12 	XUL 	GetOrMakeFont 	mozilla/gfx/thebes/src/gfxAtsuiFonts.cpp:449
13 	XUL 	gfxAtsuiFontGroup::FindATSUFont 	mozilla/gfx/thebes/src/gfxAtsuiFonts.cpp:523
14 	XUL 	gfxFontGroup::FontResolverProc 	mozilla/gfx/thebes/src/gfxFont.cpp:919
15 	XUL 	gfxPlatformMac::ResolveFontName 	mozilla/gfx/thebes/src/gfxPlatformMac.cpp:181
16 	XUL 	gfxFontGroup::ForEachFontInternal 	mozilla/gfx/thebes/src/gfxFont.cpp:886
17 	XUL 	gfxFontGroup::ForEachFont 	mozilla/gfx/thebes/src/gfxFont.cpp:762
18 	XUL 	gfxAtsuiFontGroup::gfxAtsuiFontGroup 	mozilla/gfx/thebes/src/gfxAtsuiFonts.cpp:468
19 	XUL 	gfxPlatformMac::CreateFontGroup 	mozilla/gfx/thebes/src/gfxPlatformMac.cpp:196
20 	XUL 	nsThebesFontMetrics::Init 	mozilla/gfx/src/thebes/nsThebesFontMetrics.cpp:89
21 	XUL 	nsFontCache::GetMetricsFor 	mozilla/gfx/src/nsDeviceContext.cpp:500
22 	XUL 	nsLayoutUtils::GetFontMetricsForStyleContext 	mozilla/layout/base/nsLayoutUtils.cpp:1304

Comment 3

[Gordon Thompson]

It never goes into Apple Crash reporter, just the Mozilla one. Any ideas on how I can help you further?  I've looked in /Users/gcthompson/Library/Logs/CrashReporter
but there are no pertinent logs.

Comment 4

[Kurt Weinschenker]

Not seeing this behavior on PPC Tiger with a recent (2.0b3pre (1.9.0.8pre 2009022319)) build of Camino, so if it exists, it might be Leopard or Intel Mac dependent.

I may get a chance to test this with Tiger on an Intel Mac in the next day or two, depending on stuff at work.

Comment 5

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

(In reply to comment #2)
> reporter: could you try to get an apple crash report and *attach it* - click
> "Add an attachment" - without that, we don't know much about the QD/ATS frames.

Those frames are unlikely to be helpful (which is to say they've not been useful on any of these crashes in the past, as far as I'm aware) even if we had them.

Gordon, what *would* be helpful is if you could note particular URLs you are on/are just loading when the crash occurs.  Also, have you changed any of Firefox's default font settings?  Have you checked for both duplicate and corrupt/invalid fonts in Font Book?

Comment 6

[Gordon Thompson]

One problem is that i can hit one URL and it'll crash, opening it up again and navigating to the same URL won't crash...

Comment 7

[Gordon Thompson]

Attachment: Crash report

I've been using Minefield to see if it's any more stable. It's not but this produces crash reports which may or may not be helpful...

Comment 8

[Gordon Thompson]

I don't think i've changed any preferences with regards to the fonts. I've not noticed any corrupted fonts in my font book. Not sure how I would find out though?

Cheers

Comment 9

[Gordon Thompson]

incidentally, i've just updated to 3.0.7 and the problem still remains :(

Comment 10

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

(In reply to comment #8)
> noticed any corrupted fonts in my font book. Not sure how I would find out
> though?

Sorry, Gordon; I haven't been able to check back in on this in a while :-( To check for corrupt fonts, open Font Book, select all the fonts, and choose "Validate Fonts" from the File menu.  

If there are any with problems, a window will pop up listing any fonts with warnings or errors, and you can expand the disclosure triangles to see what sorts of problems were found.

Comment 11

[John Daggett (:jtd)]

Guessing this is the same problem as bug 482128, the stack traces look very similar.  I set up a special logging build to help track down problem fonts.

Gordon, if it's not too much trouble, could you download this build to your
Desktop and run through the steps below?

  http://tinyurl.com/logcharwidth

Steps to log the error:

1. Run Terminal application
2. Enter these commands:

  cd ~/Desktop/Minefield.app/Contents/MacOS/
  export NSPR_LOG_FILE=~/Desktop/funkyfont.out
  export NSPR_LOG_MODULES=charwidth:5
  ./firefox

3. After Firefox starts, run through the sequence of steps that causes a crash
4. Attach the log file 'funkyfont.out', located on the desktop

This will dump information about which font is causing the crash.  The last
line in the file should identify the name of the problematic font.

Comment 12

[Gordon Thompson]

This build that you provided me with doesn't seem to crash. I've tried it for a couple of days and not managed to break it.

Comment 13

[Jonathan Kew [:jfkthame]]

One way to exercise the fonts a bit more would be to visit some pages that include a particularly wide variety of Unicode characters, which will force the browser to search for fonts that support them. A good starting point is
    http://alanwood.net/unicode/unicode_samples.html
and then the collection of pages for the various Unicode ranges (see the "Next" button on that page; just keep clicking to step through them).

Comment 14

[JP Rosevear [:jpr]]

Closing for a couple reasons:
1) gfxAtsuiFont is no longer used, so either its not a problem or we need new crash bugs for it with different signatures

2) It was the Song font, in which case its gone on our supported platforms and not worth caring about.

Comment 15

[JP Rosevear [:jpr]]

Actually closing.