Firefox crashes only on https://www.office.com/?auth=2
For the last couple days, this tab has been crashing constantly. Other office.com pages don't crash but https://www.office.com/?auth=2 does. I've tried starting in safe mode but it still crashes.
All Replies (8)
Hi!
We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.
The crash report is several pages of data. We need the report numbers to see the whole report.
- Enter about:crashes in the Firefox address bar and press Enter. A list of Submitted/Unsubmitted Crash Reports will appear, similar to the one shown below.
- Copy the 5 most recent Submitted Report IDs that start with bp- and then go back to your forum question and paste those IDs into the "Post a Reply" box.
Note: If a recent Report ID does not start with bp- click on it to submit the report.
(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)
Thank you for your help!
More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.
bp-f5467be9-926d-4328-b025-ef5d10190912 bp-85466b2a-ac50-4aa6-af16-03e800190912 bp-d1b139a5-148f-4fd0-b15d-325f60190912 bp-90af753f-15e8-4362-97f9-39bfc0190912 bp-2f244d84-0ecf-46dc-bcd4-e4e2c0190912
Note: http://office.com/ requires an account to sign in.
bp-f5467be9-926d-4328-b025-ef5d10190912
bp-85466b2a-ac50-4aa6-af16-03e800190912
bp-d1b139a5-148f-4fd0-b15d-325f60190912
Signature: XULContentSinkImpl::Release
Crash Reason EXCEPTION_ACCESS_VIOLATION_READ
This is for Sumo's Related Bugs 1579858 NEW --- Crash in [@ XULContentSinkImpl::Release]
Were you using Office 365 at the time?
I'm logged into office.com most of the day. I'm an admin for our 365 account. The admin page doesn't crash though. Just the one page.
hi, are you able to reliably trigger the crash with particular steps? if so, could you invest a few minutes to try and find a regression range with the tool from https://mozilla.github.io/mozregression/? we're tracking the particular problem at https://bugzilla.mozilla.org/show_bug.cgi?id=1579858 - feel free to jump in there as well if you have any more information about the problem. thank you
I see that this issue is now marked as resolved in Bugzilla. But there's no note about a fix. I see "Target Milestone: --- → mozilla71" in the note though. Does this mean we'll have to wait until version 71 before a fix is available?
that's the current state of affairs. with a crash spike this size it's more than likely that the fix will get uplifted to version 70 beta at least...