Reproducable crash in ubuntu 20.04 from Firefox 102.0 64-bit
Steps to re-create: create a new campagin attempt to change the display image using the hover-button over the image on the page.
What happens: I click the "change image" button, it gives me the os file picker. I select the file i want and click open and the file picker goes away. The "progress" bar at the top of the image shows up, changes through several states it seems. Then all screens freeze, and the computer stops responding to all output.
Supplemental info: This started happening after an update from ubuntu 18.04 lts to 21 to 22.04 lts. So I know I was not using a flatpak before and I am now.
I've attempted to use strace to figure out what's happening at the time of the freeze I'll include a picture of that if this form does not cause my entire pc to freeze. But didn't really get any useful info from that. I tried reading dmesg at the time of the crash but so far the screen freezes before any relevent information pops up. I've not been able to find any logs about whats going in previous dmesg logs.
Troubleshooting steps: I've attempted the same procedure in firefox's safe mode. This does not seem to stop the crash. I've attempted the same procedure using chrome and this works as it should.
Wšě wotmołwy (7)
Well, it seems posting the image here didn't cause a crash. But I am unable to see if the image actually got uploaded. That may point to a problem with the canvas or animations rather then the image upload it's self.
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.
The crash is halting the entire computer. As in I can't even switch to a non-gui console. (ctrl+alt+F3) or other console. It freezes solid and the hard drive light stops blinking immediately. Honestly... after having worked in computer repair and server administration for decades I've seen some pretty bad freezes. This is at the top of my list.
Firefox on the about:crashes page lists no crashes. Which makes since because of situation the bug causes. It just says: "No crash reports have been submitted." and has none to submit.
My Mozilla version 102 (on Linux) was unresponsive today and the menu looked strange, but not the system. I cannot recall the last time I had to kill Firefox. interesting... see screenshot
Try downloading Firefox from Mozilla, run it from the folder and see if you have the same issue. https://www.mozilla.org/en-US/firefox/all/#product-desktop-release
Wot jonzn4SUSE změnjeny
Now in Win11 and 102 will just freeze for about 5-10seconds and then start working again. This is the same issue in Linux. Nothing in about:crashes, but something is going on with this version. I have 69 tabs open and surfing the forum.
Wot jonzn4SUSE změnjeny
jonzn4SUSE said
My Mozilla version 102 (on Linux) was unresponsive today and the menu looked strange, but not the system. I cannot recall the last time I had to kill Firefox. interesting... see screenshot Try downloading Firefox from Mozilla, run it from the folder and see if you have the same issue. https://www.mozilla.org/en-US/firefox/all/#product-desktop-release
If you could kill firefox I would say probably not the same cascade of issues I am seeing.
I am hesitant to link the two problems since a crash can do lots of crazy stuff ONE time. But if you can get it to crash in the same way using the same steps over an over. Then yeah, probably it's a bug. Which is why I am here. I might do some more digging when I have free time to see if there are debugging tools or symbols I can use that would help. Maybe i'll fire up a vm and try in that.
It just happened again, but not sure how to provide proof of the issue with no crash reports.