Closed Bug 762750 Opened 12 years ago Closed 12 years ago

Crash in js::types::TypeMonitorResult

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Version:
16 Branch
Platform:
x86_64
All
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED DUPLICATE of bug 762473

People

(Reporter: jrmuizel, Unassigned)

References

Details

(Keywords: crash, regression, topcrash)

Crash Data

There's a spike in crashes starting from 16.0a1/20120606. The regression range for the spike is:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=a7a905fd70d5&tochange=6338a8988917

It's #10 top crasher in today's build.
Severity: normal → critical
Crash Signature: [@ js::types::TypeMonitorResult]
tracking-firefox16: --- → ?
Keywords: crash, regression, topcrash
OS: Mac OS X → All
Hardware: x86 → x86_64
Version: unspecified → 16 Branch
There have been several recent fixes that I suspect have fixed this.  I would try to reproduce, but I don't understand what "Clicking on an identifier causes this crash" means; could you elaborate?
One of the crash urls includes asus which makes me think this is another manifestation of bug 762473.
I crashed in this stack yesterday trying to repro a different bug: http://www.factorydirect.ca/ is the site that I can reproduce the crash running trunk.
Great, confirmed crash before and no crash with bug 762473, so I'll dup it.  (This will be fixed on m-c today.)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.