Closed
Bug 385600
Opened 17 years ago
Closed 17 years ago
Crash [@ gfxTextRun::CompressedGlyph::IsClusterStart]
Categories
(Core :: Layout: Text and Fonts, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 385430
People
(Reporter: MatsPalmgren_bugz, Unassigned)
References
()
Details
(Keywords: crash, testcase)
Crash Data
Attachments
(1 file)
13.51 KB,
text/plain
|
Details |
Crash [@ gfxTextRun::CompressedGlyph::IsClusterStart] STEPS TO REPRODUCE 1. load URL ACTUAL RESULT Crash. Let me know if you want details besides the attached stack. Assertions just before the crash: ###!!! ASSERTION: Invalid offset: 'aOffset <= mSkipChars->mCharCount', file gfxSkipChars.cpp, line 92 ###!!! ASSERTION: Invalid offset: 'aOffset <= mSkipChars->mCharCount', file gfxSkipChars.cpp, line 92 ###!!! ASSERTION: Negative flow length?: 'flowEndInTextRun >= transformedOffset', file nsTextFrameThebes.cpp, line 5277 PLATFORMS AND BUILDS TESTED Bug occurs in a local Firefox debug x86_64 build on Linux (Ubuntu-feisty). Bug does not occur when running a Firefox nightly build on the same host.
Flags: blocking1.9?
Reporter | ||
Comment 1•17 years ago
|
||
Comment 2•17 years ago
|
||
Bug 385430 has the same assertions and stack.
Reporter | ||
Comment 3•17 years ago
|
||
Sigh, why can't people report the crashing frame in the summary? I really don't like wasting my time on filing dupes :-(
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Comment 4•17 years ago
|
||
Sometimes I do text-in-comment searches for stack signatures and assertions to avoid filing dups. That takes like 30s per search though :(
Comment 5•17 years ago
|
||
How is a reftest file crashing not turning Tinderbox orange?
Reporter | ||
Comment 6•17 years ago
|
||
Bad luck? ;-) I'm guessing this crash only (or more frequently) occurs in debug builds, dbaron's crash looks like a 32-bit debug build so the common factor seems to be debug. None of the qm-* Tinderboxes appears to be running a debug build. I can confirm that the crash disappeared after applying the patch in bug 385344.
(In reply to comment #3) > Sigh, why can't people report the crashing frame in the summary? The top of the stack looked bogus, so I wasn't really sure if the reported frame was correct.
Comment 8•15 years ago
|
||
If you're here looking for hg changeset bb5cb73eee1a it's in bug 485600...
Reporter | ||
Updated•15 years ago
|
Flags: blocking1.9?
Assignee | ||
Updated•13 years ago
|
Crash Signature: [@ gfxTextRun::CompressedGlyph::IsClusterStart]
You need to log in
before you can comment on or make changes to this bug.
Description
•