Closed
Bug 706781
Opened 14 years ago
Closed 12 years ago
Crash in scanVisitor::VisitNode
Categories
(Core :: XPCOM, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: scoobidiver, Unassigned)
Details
(Keywords: crash, regression)
Crash Data
It first appeared in 11.0a1/20111126.
The regression range is:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=84117219ded0&tochange=c58bad0b4640
Signature scanVisitor::VisitNode(PtrInfo*)
UUID b10b22a2-0326-4a6a-a247-38f992111130
Date Processed 2011-11-30 01:05:36.772990
Uptime 1544
Last Crash 2.5 days before submission
Install Age 41.9 minutes since version was first installed.
Install Time 2011-11-30 08:23:27
Product Firefox
Version 11.0a1
Build ID 20111129031019
Release Channel nightly
OS Windows NT
OS Version 6.1.7601 Service Pack 1
Build Architecture amd64
Build Architecture Info family 6 model 15 stepping 11
Crash Reason EXCEPTION_ACCESS_VIOLATION_READ
Crash Address 0x36c053d8
App Notes AdapterVendorID: 1002, AdapterDeviceID: 68be, AdapterSubsysID: 21e91458, AdapterDriverVersion: 8.911.0.0
D2D? D2D+
DWrite? DWrite+
D3D10 Layers? D3D10 Layers+
EMCheckCompatibility False
Frame Module Signature [Expand] Source
0 xul.dll scanVisitor::VisitNode xpcom/base/nsCycleCollector.cpp:1984
1 xul.dll nsCycleCollector::ScanRoots xpcom/base/nsCycleCollector.cpp:2033
2 xul.dll xul.dll@0x10ac2f
3 xul.dll nsCycleCollector::BeginCollection xpcom/base/nsCycleCollector.cpp:2872
4 xul.dll xul.dll@0x11eacf
More reports at:
https://crash-stats.mozilla.com/report/list?range_value=30&range_unit=days&signature=scanVisitor%3A%3AVisitNode%28PtrInfo*%29
| Reporter | ||
Comment 1•14 years ago
|
||
It's #30 top crasher in 12.0a1 and happens only with 64-bit builds.
Version: Trunk → 11 Branch
Comment 2•14 years ago
|
||
pretty rare now. only 4 crashes per month for FF14 and FF13. ANd all are x86. bp-fa96e28a-aa24-4e6a-8ef0-30b7e2120804
https://crash-stats.mozilla.com/query/query?product=Firefox&version=ALL%3AALL&range_value=1&range_unit=weeks&date=08%2F08%2F2012+12%3A31%3A55&query_search=signature&query_type=contains&query=scanVisitor%3A%3AVisitNode&reason=&build_id=&process_type=any&hang_type=any&do_query=1
perhaps the signature has changed?
Comment 3•12 years ago
|
||
This doesn't look like a problem any more. The signature may have just changed.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•