Closed Bug 983708 Opened 11 years ago Closed 4 years ago

crash in nsNodeInfoManager::GetNodeInfoInnerHashValue(void const*)

Categories

(Core :: DOM: Core & HTML, defect, P5)

All
macOS
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox48 --- affected
firefox49 --- affected
firefox-esr45 --- affected
firefox-esr52 --- affected

People

(Reporter: ehsan.akhgari, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is report bp-60e50eb7-aae9-4713-abdd-7854c2140314. ============================================================= The crash address is at 0x8, and mName cannot be null, so perhaps mStringName is null?
https://crash-stats.mozilla.com/report/list?product=Firefox&signature=nsNodeInfoManager%3A%3AGetNodeInfoInnerHashValue%28void+const*%29 says the signature happens on all OSes and versions at low volume, but the addresses vary and most are actually at 0x4 while Mac seems to always be 0x8, are the non-Mac crashes the same issue or something different?
Windows users are probably going to be running a binary where one word is 32 bits while Mac users will be running 64 bit.
Crash Signature: [@ nsNodeInfoManager::GetNodeInfoInnerHashValue(void const*)] → [@ nsNodeInfoManager::GetNodeInfoInnerHashValue(void const*)] [@ nsNodeInfoManager::GetNodeInfoInnerHashValue]
Crash volume for signature 'nsNodeInfoManager::GetNodeInfoInnerHashValue': - nightly (version 50): 0 crashes from 2016-06-06. - aurora (version 49): 1 crash from 2016-06-07. - beta (version 48): 34 crashes from 2016-06-06. - release (version 47): 135 crashes from 2016-05-31. - esr (version 45): 8 crashes from 2016-04-07. Crash volume on the last weeks: W. N-1 W. N-2 W. N-3 W. N-4 W. N-5 W. N-6 W. N-7 - nightly 0 0 0 0 0 0 0 - aurora 0 0 1 0 0 0 0 - beta 5 5 7 3 2 7 4 - release 18 15 21 16 21 15 15 - esr 2 0 1 1 1 0 1 Affected platforms: Windows, Mac OS X, Linux
FF 52ESR and 57 is affected. d62b2ba8-dfdf-40d8-b401-e8ed30180109 2018-01-09 08:27:11 Firefox 57.0.4 20180103231032 Windows NT EXCEPTION_ACCESS_VIOLATION_WRITE 0x3305c2c1 2018-01-05 08:23:17 659b4518-f984-4f5c-b58c-0c12b0180113 2018-01-13 15:16:18 FennecAndroid 57.0.1 20171129020910 Android SIGSEGV 0xfffffffa 2017-12-07 20:46:26 2abc3ae9-6211-43df-8a88-7ae220180121 2018-01-21 00:30:54 Firefox 54.0.1 20170628075643 Windows NT EXCEPTION_ACCESS_VIOLATION_WRITE 0xffffffff8bc35dc1 2017-08-14 10:44:54 4b0b9611-dd5c-40df-8822-569710180408 2018-04-08 00:49:57 Firefox 52.7.3esr 20180322140748 Windows NT EXCEPTION_ACCESS_VIOLATION_READ 0x4 2018-03-27 04:12:46 ba732003-a549-451d-9d98-3a2fb0180401 2018-04-01 10:30:40 Firefox 52.7.3esr 20180322140748 Windows NT EXCEPTION_ACCESS_VIOLATION_READ 0x4 2018-03-27 17:24:18 c9844136-8732-4c8a-b0d0-6e7cf0180329 2018-03-29 02:57:33 Firefox 52.7.3esr 20180322140748 Mac OS X EXC_BAD_ACCESS / KERN_INVALID_ADDRESS 0x8 2018-03-27 15:54:20 8596d967-57d9-4ce4-998b-8e32f0180328 2018-03-28 11:52:01 Firefox 52.7.2esr 20180315163333 Windows NT EXCEPTION_ACCESS_VIOLATION_READ 0x4 2018-03-26 13:29:09
Priority: -- → P5
Component: DOM → DOM: Core & HTML

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.