User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0a1) Gecko/20110924 Firefox/9.0a1 Build ID: 20110924030858 Steps to reproduce: Visit http://www.ro.me/ Actual results: Nightly crashed :( Expected results: Less crashing.

Some other reports. Two of them are a plugin hang, not sure if related. bp-7358f09e-2486-471b-88f3-7681d2110925 bp-03cb0001-33c6-470d-96f8-4dc312110925 bp-5c9de4c3-fe69-4fe5-85dd-6cf6f2110925 bp-3bfa4f3e-7552-4d44-be82-e16912110925

This WORKSFORME using a graphics adapter for which webgl is officially supported. Please post the output of the Graphics section of form the about:support page.

His setup is officially supported: device 0112 is Sandy Bridge, and driver version 8.15.10.2509 is recent enough (min required on his setup is 8.15.10.2202). Too bad that the stacks in these crash reports are useless (they point to the crashreporter itself). +CC Ted to figure why a crash stack would point to the crash reporter?? I see these crashes are on Nightly. Can you reproduce with a more stable channel?

Hm... this just occurred to me: from the crash reports: Winsock LSP MSAFD Tcpip [TCP/IP] : 2 : 1 : %SystemRoot%\system32\mswsock.dll MSAFD Tcpip [UDP/IP] : 2 : 2 : MSAFD Tcpip [RAW/IP] : 2 : 3 : %SystemRoot%\system32\mswsock.dll MSAFD Tcpip [TCP/IPv6] : 2 : 1 : MSAFD Tcpip [UDP/IPv6] : 2 : 2 : %SystemRoot%\system32\mswsock.dll MSAFD Tcpip [RAW/IPv6] : 2 : 3 : RSVP TCPv6 Service Provider : 2 : 1 : %SystemRoot%\system32\mswsock.dll RSVP TCP Service Provider : 2 : 1 : RSVP UDPv6 Service Provider : 2 : 2 : %SystemRoot%\system32\mswsock.dll RSVP UDP Service Provider : 2 : 2 : This 'Winsock LSP' thing is often found in trojan-infested machines, and is very correlated with Firefox topcrashers. Moreover the [@ _SEH_epilog4] signature is actually a major crash signature: https://crash-stats.mozilla.com/report/list?range_value=7&range_unit=days&date=2011-09-24&signature=_SEH_epilog4&version=Firefox%3A6.0.2 and is filed as bug 679846, suspected to be "malware related". -> looks like it might be time to inspect your machine ;-)

Bug 679846 comment 10 suggests that the crash signature was unreliable, reopening. Bug 683162 just got fixed so if you can retry tomorrow, there is a fair chance that we might get a much better stack.

Sure.

(In reply to Benoit Jacob [:bjacob] from comment #3) > Too bad that the stacks in these crash reports are useless (they point to > the crashreporter itself). +CC Ted to figure why a crash stack would point > to the crash reporter?? This is almost certainly bug 683162, which should be making it into Socorro production very soon. We can get those crash reports reprocessed when it gets there to get useful stacks out of them.

Content crash occurs on mobile. Crash stack is shown as bug 687554; not sure if windows is seeing the same type of crash stack?

I managed to get it to crash for me with current nightly. This stack looks more useful. bp-eea93b37-c932-411d-849e-170402110927

which makes it appear this is probably a dupe of bug 672870.

Hmm that bug was filed on the same site. Definitely a dupe.