Closed Bug 606078 Opened 14 years ago Closed 8 years ago

ABORT: Starting new frame but not done with old one!: '!mInFrame'

Categories

(Core :: Graphics: ImageLib, defect)

x86_64
macOS
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME
Tracking Status
fennec - ---

People

(Reporter: jdm, Unassigned)

Details

(Keywords: crash)

Attachments

(1 file)

Attached file Backtrace
Running a recent fennec build, I went to geocities.co.uk, watch the throbber keep spinning indefinitely, brought up the awesomescreen and fennec crashed with the attached backtrace.  Can't reproduce, however.
I realize that blocking without STR is not likely, but I'd like to get this on the radar.  Chrome process crashes are not fun.
tracking-fennec: --- → ?
2.0 for now, might move up to b3 if it starts showing up in top crashes
tracking-fennec: ? → 2.0+
Are the platform settings on this correct?
More or less, yes.
Hardware: x86 → x86_64
(In reply to comment #3)
> Are the platform settings on this correct?

(In reply to comment #4)
> More or less, yes.

Ahh... so this is actually OS X only? not blocking then.
tracking-fennec: 2.0+ → 2.0-
fyi, crash automation hit this with a Beta debug build from this morning on xp at http://www.netshoes.com.br/produto/004-9649-028-40?foto=2 but I couldn't reproduce it with local builds from yesterday. I'll rebuild etc and try again.
Severity: normal → critical
We don't see this in automation anymore.
No use keeping this around, in that case.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: