Crash [@ nsGlobalWindow::GetContextInternal() ]

NEW
Unassigned

Status

()

Core
DOM
--
critical
8 years ago
3 years ago

People

(Reporter: gadjo, Unassigned)

Tracking

({crash})

Trunk
x86
Windows 7
crash
Points:
---

Firefox Tracking Flags

(blocking2.0 -, status2.0 wanted)

Details

(crash signature)

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101017 Firefox/4.0b8pre
Build Identifier: 

Signature	nsGlobalWindow::GetContextInternal()
UUID	9298b0ac-6229-429c-bb79-181082101017
Time 	2010-10-17 04:33:59.19444
Uptime	23858
Last Crash	236845 seconds (2.7 days) before submission
Install Age	28470 seconds (7.9 hours) since version was first installed.
Product	Firefox
Version	4.0b8pre
Build ID	20101016041245
Branch	2.0
OS	Windows NT
OS Version	6.1.7600
CPU	x86
CPU Info	GenuineIntel family 6 model 23 stepping 10
Crash Reason	EXCEPTION_ACCESS_VIOLATION_READ
Crash Address	0x30
User Comments	
App Notes 	AdapterVendorID: 1002, AdapterDeviceID: 9505
Processor Notes 	
EMCheckCompatibility	False

Frame 	Module 	Signature [Expand] 	Source
0 	xul.dll 	nsGlobalWindow::GetContextInternal 	dom/base/nsGlobalWindow.h:470
1 	xul.dll 	nsWindowSH::NewResolve 	dom/base/nsDOMClassInfo.cpp:6495
2 	xul.dll 	xpc::ResolveNativeProperty 	js/src/xpconnect/wrappers/XrayWrapper.cpp:228
3 	xul.dll 	xpc::XrayWrapper<JSCrossCompartmentWrapper,xpc::CrossCompartmentXray>::getPropertyDescriptor 	js/src/xpconnect/wrappers/XrayWrapper.cpp:551
4 	xul.dll 	xul.dll@0xcc11cf 	
5 	mozjs.dll 	js::JSProxyHandler::get 	js/src/jsproxy.cpp:118


Reproducible: Didn't try
Severity: normal → critical
Keywords: crash
Version: unspecified → Trunk
Status: UNCONFIRMED → NEW
blocking2.0: --- → ?
Ever confirmed: true
This one is probably compartment related, but need more stats here.

Comment 2

8 years ago
Looks like there have only been 8 crashes is total for this one.
(Reporter)

Comment 4

8 years ago
Unfortunately not, as far as I remember it crashed right after some popup window has opened, but I guess it's not enough information

Updated

8 years ago
Component: General → DOM
QA Contact: general → general
Not blocking, we had a spike of crashes on 10/12, but now we're seeing only one or two a day, so this is a really low volume crash. If we get more data on how to reproduce this and a fix, I'd love to take it for 2.0 though.
blocking2.0: ? → -
status2.0: --- → wanted
(Assignee)

Updated

7 years ago
Crash Signature: [@ nsGlobalWindow::GetContextInternal() ]

Comment 6

7 years ago
Additional crashes:
<https://crash-stats.mozilla.com/report/index/bp-446e7697-6b3c-4b7d-bed6-e567b2111208#modver>

And I replicated this morning:
<https://crash-stats.mozilla.com/report/index/bp-c40bff51-43ea-4e06-90fb-319332111209>

Printing a page to cups-pdf printer via the 'Print' button on the page.
Unfortunately the page is https and requires a member login, so I can't
supply a URL for testing. Note: printing from File|Print|cups-pdf works
fine. I tried that before using the 'Print' button on the page to
replicate the crash.

Yesterday the first crash resulted in:
<https://crash-stats.mozilla.com/report/index/bp-aa70df3b-d05d-49d1-907f-5f4172111208> (@ JSCompartment::wrap).

Updated

3 years ago
Crash Signature: [@ nsGlobalWindow::GetContextInternal() ] → [@ nsGlobalWindow::GetContextInternal() ] [@ nsGlobalWindow::GetContextInternal ]
You need to log in before you can comment on or make changes to this bug.