1144290 - crash in shutdownhang | mozilla::dom::Element::SetAttr(int, nsIAtom*, nsIAtom*, nsAString_internal const&, bool)

Status: RESOLVED WONTFIX

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

Description

[u279076]

This bug was filed from the Socorro interface and is 
report bp-5a7d76c4-51bf-4860-bc86-dce462150310.
=============================================================
0 	xul.dll 	mozilla::`anonymous namespace'::RunWatchdog(void*) 	toolkit/components/terminator/nsTerminator.cpp
1 	nss3.dll 	_PR_NativeRunThread 	nsprpub/pr/src/threads/combined/pruthr.c
2 	nss3.dll 	pr_root 	nsprpub/pr/src/md/windows/w95thred.c
3 	msvcr120.dll 	_callthreadstartex 	f:\dd\vctools\crt\crtw32\startup\threadex.c:376
4 	msvcr120.dll 	msvcr120.dll@0x2c000 	
5 	kernel32.dll 	BaseThreadInitThunk 	
6 	ntdll.dll 	__RtlUserThreadStart 	
7 	ntdll.dll 	_RtlUserThreadStart 	
=============================================================
More reports: https://crash-stats.mozilla.com/report/list?product=Firefox&signature=shutdownhang+|+mozilla%3A%3Adom%3A%3AElement%3A%3ASetAttr%28int%2C+nsIAtom*%2C+nsIAtom*%2C+nsAString_internal+const%26%2C+bool%29

Volume: 622 crashes in the last week

Platform Breakdown: 
* 65% on Windows 7
* 33% on other Windows
* 1% on Mac OS X
* 0% on Linux

Product Breakdown:
* 99% on Firefox 36.0.1
* 1 crash on Firefox 36 Beta
* 1 crash on Firefox 37 Beta
* 0 crashes on any other product

GPUs:
* Intel accounts for the top 12 reported cards
* AMD is the second most reported

I don't have any leads with this crash but I'm reporting it since it meets our 1% threshold for reporting. Top URLs are facebook, google, and yahoo. Unfortunately there is nothing in the comments apart from crashing on shutdown.

Comment 1

[u279076]

[Tracking Requested - why for this release]: this first shows up with Firefox 36 so this might be a regression.

Comment 2

[Olli Pettay [:smaug][[e-mail]]]

Again one of these odd crashes where stack trace doesn't really make sense - or at least
it doesn't tell why crash is reported in Element::SetAttr

Comment 3

[u279076]

(In reply to Olli Pettay [:smaug] from comment #2)
> Again one of these odd crashes where stack trace doesn't really make sense -
> or at least
> it doesn't tell why crash is reported in Element::SetAttr

Yeah, is there something that happened in Firefox 36 that is making these shutdownhang crashes show up much more frequently?

Comment 4

[Mats Palmgren (inactive)]

This might be it:
https://www-dev.allizom.org/en-US/firefox/36.0/releasenotes/
"Shut down hangs will now show the crash reporter before exiting the program"

Comment 5

[u279076]

(In reply to Mats Palmgren (:mats) from comment #4)
> This might be it:
> https://www-dev.allizom.org/en-US/firefox/36.0/releasenotes/
> "Shut down hangs will now show the crash reporter before exiting the program"

Ah okay, so be a case of something being reported but not necessarily happening more frequently.

Comment 6

[Sylvestre Ledru [:Sylvestre]]

Closing because no crash reported since 12 weeks.