User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0 Build ID: 20160604131506 Steps to reproduce: Clicked either the "Restart Firefox" or "Quit" button in the Firefox Crash Reporter application. Unfortunately I don't know how to reliably reproduce this. The crash reporter only runs when Firefox crashes which is itself pretty random, and the crash reporter doesn't *always* lock up although I have now experienced this behavior multiple times. Actual results: Crash Reporter stopped responding and had to be killed via task manager. Expected results: Crash Reporter should exit and possibly restart Firefox depending which button was clicked.
Hi Andy, I tried to test this issue on Windows 10 x64 with FF 48 and I can't reproduce it. Here are the steps that I follow: 1. Install an add-on that allows you to crash Firefox when you want. You can use https://addons.mozilla.org/en-US/firefox/addon/crash-me-now-simple/?src=ss After you install this add-on you can find it in Menu-> Customize 2. Crash the browser and after you receive the Mozilla Crash Report please write below Details "TEST" and then please choose "Restart Firefox" or "Quit Firefox". For me both buttons are working. NOTE: I use new profile. Please try the above steps and also please try with new profile, here is a link that can help you to create a new profile: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles?redirectlocale=en-US&redirectslug=Managing-profiles#w_starting-the-profile-manager
Hi, Marking this as Resolved: Incomplete due to the lack of response from Andy. If the issue is still reproducible with the latest Firefox version, feel free to reopen the bug with more information.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
I'm not sure what the right answer is here. It's sort of reproducible? Using the Crash Me Now add-on I can reproduce the issue but ONLY after Firefox first crashes "naturally". If I re-open Firefox after an unintentional crash and then immediately crash it again with the add-on, I get the stopped-responding behavior about 10% of the time. If Firefox hasn't experienced a random crash recently then I cannot reproduce the behavior by simply using the add-on. I realize "randomly reproducible" is not exactly ideal. If it's useful info, every time I've seen this behavior the original crash happened during netflix playback.
For now there are not many details that can help us to determine what is going on here, also this is an edge case.
You need to log in before you can comment on or make changes to this bug.