Crash Signature: [@ XPCWrappedNativeScope::GetGlobalJSObject() ]
Crash Signature: [@ XPCWrappedNativeScope::GetGlobalJSObject() ] → [@ XPCWrappedNativeScope::GetGlobalJSObject() ] [@ XPCWrappedNativeScope::GetGlobalJSObject ]
Hi Jonatan, Could you please provide us some information about how to reproduce this issue? Something like the environment where it took place, what add-ons/plugins are enabled, how often does it happen and when does it happen. Can you please try to reproduce this with a new clean Firefox profile, safe mode enabled? For example, if this crash takes place when you start Firefox, it may be an add-on issue. Any other additional information that you believe it could help to reproduce on our end it will be welcomed. Thanks.
[testday-20151211] Hello Jonathan, You obtained your bug using the OS Windows NT Version 6.3.9600 (more popularly known as Windows 8.1.) Would greatly appreciate the following additional information: 1. The version of Windows 8.1 you were running i.e. was it Windows 8.1, Windows 8.1 Pro, or Windows 8.1 Enterprise? 2. Could you please provide detailed steps to reproduce this bug to assist in trying to reproduce it? 3. Screenshots of what you saw on your computer screen when the bug occurred. 4. Please provide a general description of what operation you were trying to perform with Firefox when it occurred. 5. Does the bug happen with the latest Nightly? 6. Does the bug happen when running in Safe Mode? 7. Does the bug happen in other browsers? 8. On which versions of Firefox does this bug occur?
Please provide some information.
Since the reporter didn't provide the requested information, I will mark this as RESOLVED INCOMPLETE. If you still encounter this issue, please feel free to reopen this bug or file a new one, and provide all necessary steps to reproduce.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
Moving from Core::Untriaged to Core::General https://bugzilla.mozilla.org/show_bug.cgi?id=1407598
Component: Untriaged → General
You need to log in before you can comment on or make changes to this bug.