Closed Bug 1209186 Opened 9 years ago Closed 8 years ago

crash in nsTextFrame::TrimTrailingWhiteSpace - startup crash in safe mode

Categories

(Core :: Layout: Images, Video, and HTML Frames, defect)

43 Branch
Unspecified
Windows NT
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: milan, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-44288652-b83f-4cb0-960e-bb9002150928.
=============================================================

This is not frequent at all, but it is a startup crash in the safe mode, and is probably worth a look at the code.
Flags: needinfo?(bugs)
Crashing address indicates that Firefox came off the rails much earlier than the last function in the stack. This looks similar to bug 1063052 though this crashes several frames inside ::BoxReflow(). David: have you seen this one before?
Flags: needinfo?(bugs) → needinfo?(dmajor)
There's a single-bit error in the crashing instruction, which tends to indicate bad RAM. 

The code was supposed to do this vtable call:
ff5018          call    qword ptr [rax+18h]
but the machine actually did:
ff5019          call    qword ptr [rax+19h]
which produced a bogus address.

Milan, is this your own machine? i.e. are you able to run memory diagnostics?
Flags: needinfo?(dmajor)
No, this is just a random crash I pulled in because it was tagged as "in safe mode".  Doesn't sound like there is cause for concern given the bad RAM part...
Ok. Btw I forgot to mention, I did confirm that all the instances of this on nightly came from a single installation.
Doesn't seem worth tracking based on comment 2 and 4.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
Component: Layout: HTML Frames → Layout: Images
Product: Core Graveyard → Core
You need to log in before you can comment on or make changes to this bug.