Closed Bug 590106 Opened 14 years ago Closed 14 years ago

Firefox 4.0b5pre Crash Report [@ UnlockEnumerator(imgIRequest*, unsigned int, void*) ]

Categories

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

x86
Windows 7
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 589469
Tracking Status
blocking2.0 --- beta7+

People

(Reporter: cbook, Unassigned)

References

()

Details

(Keywords: crash)

Crash Data

Bug 589469#c5 - this might be a dupe of that bug.
Not sure if my crashes on Mac OS X (10.6) are related, but I've been getting a lot of the same crashes on trunk in the last day or so. They seem to occur spontaneously with no user interaction.

http://crash-stats.mozilla.com/report/index/bp-90efe4ba-49cb-4ab7-8c97-bde0a2100826
#2 in top crashers for b5pre
blocking2.0: --- → ?
A fix for Bug 589469 was just checked in, so we should see if this drops off in the nightlies starting tomorrow.
blocking2.0: ? → beta7+
Component: General → Layout: Images
QA Contact: general → layout.images
http://crash-stats.mozilla.com/report/list?range_value=30&range_unit=days&date=2010-09-05%2004%3A00%3A00&signature=UnlockEnumerator%28imgIRequest*%2C%20unsigned%20int%2C%20void*%29&version=Firefox%3A4.0b5pre
shows that this crash was present in nightlies from August 18 to August 27 (inclusive).

Marking WORKSFORME, though bholley may know what fixed it.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Er, actually, that was a bad choice of query since it was version dependent.  Here's a query for all crashes with branch set to 2.0:

http://crash-stats.mozilla.com/report/list?range_value=30&range_unit=days&date=2010-09-05%2004%3A00%3A00&signature=UnlockEnumerator%28imgIRequest*%2C%20unsigned%20int%2C%20void*%29&branch=2.0

It yields the same date range, though, so we're ok.
the volume is definitely down from the 170-33 crashes per day but it looks like there are still a few crashes around with this signature.  Are they the same crash?

date     tl crashes at, count build, count build, ...
         UnlockEnumerator.imgIRequest...unsigned.int..void..

20100908 1 ,1 4.0b52010083108  like http://crash-stats.mozilla.com/report/index/9163fd6f-0982-4759-ab4a-415662100908

20100909 10 ,9 4.0b5pre2010082104,1 4.0b52010083108
20100910 17 ,1 4.0b5pre2010082404,8 4.0b5pre2010082104,8 4.0b52010083108
20100911 9 ,1 4.0b6pre2010091104,8 4.0b52010083108
20100912 6 ,1 4.0b5pre2010082506,5 4.0b52010083108
20100913 12 ,1 4.0b5pre2010082004,8 4.0b52010083108,3 4.0b5pre2010082704
20100914 5 ,4 4.0b52010083108,1 4.0b5pre2010082305
20100915 3 ,1 4.0b7pre2010091404,1 4.0b62010091408,1 4.0b52010083108

4.0b7pre like http://crash-stats.mozilla.com/report/index/30279d0a-137c-49af-8d9c-502f62100915
http://crash-stats.mozilla.com/report/list?range_value=30&range_unit=days&date=2010-09-25%2004%3A00%3A00&signature=UnlockEnumerator%28imgIRequest*%2C%20unsigned%20int%2C%20void*%29&branch=2.0
shows that, other than the crashes on 4.0b5 itself (which were presumably built from source from the 27th?) and one crash on 4.0b6 (which is a revision of b5), there have only been two total crashes on newer builds:

bp-fab18913-fb3f-4af0-b2ce-73d452100911
bp-30279d0a-137c-49af-8d9c-502f62100915

I don't think that deserves investigation unless there are steps to reproduce.
I guess b5 and b6 should have had the fix, though.

Still, it's pretty low crash volume.
This is the same issue as bug 589469, whose fix landed on the 27th.
Resolution: WORKSFORME → DUPLICATE
Crash Signature: [@ UnlockEnumerator(imgIRequest*, unsigned int, void*) ]
Product: Core → Core Graveyard
Product: Core Graveyard → Core
You need to log in before you can comment on or make changes to this bug.