Closed Bug 1207173 Opened 10 years ago Closed 10 years ago

crash in mozilla::layers::WalkTheTree<T>

Categories

(Core :: Graphics: Layers, defect)

43 Branch
Unspecified
Windows NT
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 1206524

People

(Reporter: tracy, Unassigned)

Details

(Keywords: crash, topcrash)

This bug was filed from the Socorro interface and is report bp-b9613a10-f0f3-4b37-bbcb-48fbf2150922. ============================================================= This exploded with builds on all platforms as of build 2015092003 with 68 crashes. However, the builds from yesterday only had 10 crashes reported. On Mac 10.9.5, I hit this once with each Nightly build from 9/20 and 9/21, just loading the new tab tiles page soon after browser start.
I'm pretty sure it's the same issue as in bug #1206524.
Status: NEW → RESOLVED
Crash Signature: [@ mozilla::layers::WalkTheTree<T>]
Closed: 10 years ago
Resolution: --- → DUPLICATE
I don't understand why you're wiping the crash signatures from any bug with a signature associated with the random crash bug. It makes it a challenge to look at crash stats and have to recall if anyone has filed a bug on a particular signature. By leaving the signature in duped bugs, since you've wiped all signatures from the random crash bug, a bread crum trail can be picked up in crash stats and followed to the source.
Crash Signature: [@ mozilla::layers::WalkTheTree<T>]
It's because posting crash report signature doesn't make sense in this specific case, as it will be probably over 100 or more of them. Please see also Bug #1206524 Comment #10.
Crash Signature: [@ mozilla::layers::WalkTheTree<T>]
I'm sorry, I didn't mean we should track the long tail of signatures associated with this. But it wouldn't have hurt a thing to leave the signatures in the several bugs that people already took the time to report and/or that made topcrash criteria. Anyway, the noise on crash stats will go away in a few days. I'll check back to it next week.
You need to log in before you can comment on or make changes to this bug.