搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Firefox 102 and 102.0.1 crashes after some Time! Please Help!

  • 16 个回答
  • 1 人有此问题
  • 10 次查看
  • 最后回复者为 jonzn4SUSE

more options

Hello :)

Firefox 102.0.1 crashes after some Time. Firefox then is unable to switch between Tabs and stuck at the opened Website.

For testing Purpose i start over with a new profile and did not install any Add-ons. The behavior was the same, it crashes after some hours.

My System is Ubuntu Mate (Ubuntu with Mate Desktop) in Version 20.04.

Here has someone the same problem: -> https://bbs.archlinux.org/viewtopic.php?id=277649

Thanks for any suggestions.

Hello :) Firefox 102.0.1 crashes after some Time. Firefox then is unable to switch between Tabs and stuck at the opened Website. For testing Purpose i start over with a new profile and did not install any Add-ons. The behavior was the same, it crashes after some hours. My System is Ubuntu Mate (Ubuntu with Mate Desktop) in Version 20.04. Here has someone the same problem: -> https://bbs.archlinux.org/viewtopic.php?id=277649 Thanks for any suggestions.

由Kater于修改

所有回复 (16)

more options

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.

  1. 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.
  2. 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.)

Fx64Beta-aboutcrashes-unsubmitted

Thank you for your help!

More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.

more options

Dear Paul,

Yet there are no crash report to post. At the next fail of Firefox i will not close it and wait some time.

I'll came back.

more options

I would try Firefox from Mozilla and see if you have the same issues. https://www.mozilla.org/en-US/firefox/all/#product-desktop-release Have you tried running Firefox in Safe Mode to see if you still have the same issues? https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode Are you comfortable with strace to see what's causing the crash?

more options

Thank you jonzn4SUSE,

The tarball Firefox from Mozilla Website freezes in Safe Mode and came back within approx 1 Minute.

Strace you can found here: -> https://pastebin.com/p8D2pXjT

由Kater于修改

more options

Thank you jonzn4SUSE,

The Mozilla Tarball freezes in Safe Mode.

Edit: i have to test it again....

由Kater于修改

more options

Here the Strace without Safe Mode:

https://pastebin.com/VGVj7Z2i

Browser stopped and won't return!

Thanks for any help!

more options

Kater said

Thank you jonzn4SUSE, The Mozilla Tarball freezes in Safe Mode. Edit: i have to test it again....

Yes, the GUI freezes (and and Youtube continues to play normally).

Here ist the strace output in Safe Mode:

https://pastebin.com/QsX7gvup

more options

Can you get time stamps in the strace? Need to know exactly what time the crash happened and then we see what's happening at that time. see screenshots

由jonzn4SUSE于修改

more options

I would also fire up a live usb stick or vm and try another OS just to compare. wink wink  ;-)) https://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-KDE-Live-x86_64-Current.iso

Or just switch to KDE or Gnome.

Operating System: openSUSE Tumbleweed 20220711 KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.9-2-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-4810MQ CPU @ 2.80GHz Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 Manufacturer: Hewlett-Packard Product Name: HP ZBook 17 G2

由jonzn4SUSE于修改

more options

Thanks for your Support!

Here is the strace you asked for:

https://drive.google.com/file/d/18-dj0GUni5dMdh1Tlvfi89OHANl4phNn/view?usp=sharing

(Its only the last 215000 lines, if you need the whole file please tell me)

The openSUSE live System i'll test tomorrow.

more options

From your output, I googled this madvise(0x7ff8eceed000, 4096, MADV_DONTNEED) = 0 and came across this --> https://github.com/gperftools/gperftools/issues/1073

由jonzn4SUSE于修改

more options

Kater said

Thank you jonzn4SUSE, The Mozilla Tarball freezes in Safe Mode. Edit: i have to test it again....

This is bad, but a good thing that both distro and Mozilla Firefox crash. What version of Firefox did you try? Nightly is my daily driver a I've had no issues, but I had to kill 102.0 in Windows and Linux. I can't recall the last time I had to do that. Your output ends with madvise(0x7ff909e91000, 16384, MADV_DONTNEED) = 0 I would head over to your Ubuntu forum and ask about this.

Google search on Madvdontneed

由jonzn4SUSE于修改

more options

Thanks again for your Support, jonzn4SUSE!

I have moved from Ubuntu Mate 20.04 to 22.04, the error also happens there!

I have asked on my ubuntu Forum and i will return for clearance if the error gets solved.

more options

Cool. In the mean time openSUSE is waiting for you.  ;-))

more options

The Problem still remains on Firefox 105.0.1. I cant use Firefox any more and i have switched to a chromium-based Browser for now.

Is Mozilla aware of the problem?

more options

Kater said

Thanks again for your Support, jonzn4SUSE! I have moved from Ubuntu Mate 20.04 to 22.04, the error also happens there! I have asked on my ubuntu Forum and i will return for clearance if the error gets solved.

Issue happens with distro and Mozilla version of Firefox on different versions of ubuntu. Sounds like an OS issue. Try reporting a bug and see what they say.