Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox crashing on launch after updates

  • 1 பதிலளி
  • 0 இந்த பிரச்னைகள் உள்ளது
  • 37 views
  • Last reply by J

As title: after running updates, Firefox consistently crashes when launching.

To give more concrete details:

-Running on Linux, specifically KDE Fedora 42. Firefox was updated to 142 from 141, alongside various other updates. -When launching Firefox from any source (directly, through a link, through the terminal etc.), the only window that appears is the crash reporter. -This issue occurs when launching in safe mode. Removing and reinstalling Firefox, including deleting the entire .mozilla folder in Home at the same time does not resolve the issue. I am unable to test rolling Firefox back to 141. -When attempting to launch from the terminal (safe mode or otherwise), the following is output (personal info redacted):


restorecon: SELinux: Could not get canonical path for /home/[username]/.mozilla/firefox/*/gmp-widevinecdm/* restorecon: No such file or directory.

/usr/include/c++/15/array:210: constexpr std::array<_Tp, _Nm>::value_type& std::array<_Tp, _Nm>::operator[](size_type) [with _Tp = HeaderBarButtonType; long unsigned int _Nm = 3; reference = HeaderBarButtonType&; size_type = long unsigned int]: Assertion '__n < this->size()' failed.

Redirecting call to abort() to mozalloc_abort

[ExceptionHandler generates a minidump etc.]

Gtk-Message: [timestamp]: Failed to load module "appmenu-gtk-module"


(I would note that to the best of my knowledge I had not included a plugin for decoding widevine in my Firefox setup, and certainly the Firefox 141 instance on the device being used to write this post (same OS) does not include it) -The crash files in the .mozilla folder, meanwhile, consistently list a segfault at address 0x0.

Any advice on diagnosing/solving this issue would be greatly appreciated. Let me know if there's any other information that would be helpful.

If it would be more appropriate, I could report this through Mozilla's bugzilla instance, but given the issue seems to be very niche (Fedora's ABRT shows a total of 5 unique affected users in the last few days) I am unsure whether flagging this there would be appropriate.

As title: after running updates, Firefox consistently crashes when launching. To give more concrete details: -Running on Linux, specifically KDE Fedora 42. Firefox was updated to 142 from 141, alongside various other updates. -When launching Firefox from any source (directly, through a link, through the terminal etc.), the only window that appears is the crash reporter. -This issue occurs when launching in safe mode. Removing and reinstalling Firefox, including deleting the entire .mozilla folder in Home at the same time does not resolve the issue. I am unable to test rolling Firefox back to 141. -When attempting to launch from the terminal (safe mode or otherwise), the following is output (personal info redacted): --------- restorecon: SELinux: Could not get canonical path for /home/[username]/.mozilla/firefox/*/gmp-widevinecdm/* restorecon: No such file or directory. /usr/include/c++/15/array:210: constexpr std::array<_Tp, _Nm>::value_type& std::array<_Tp, _Nm>::operator[](size_type) [with _Tp = HeaderBarButtonType; long unsigned int _Nm = 3; reference = HeaderBarButtonType&; size_type = long unsigned int]: Assertion '__n < this->size()' failed. Redirecting call to abort() to mozalloc_abort [ExceptionHandler generates a minidump etc.] Gtk-Message: [timestamp]: Failed to load module "appmenu-gtk-module" --------- (I would note that to the best of my knowledge I had not included a plugin for decoding widevine in my Firefox setup, and certainly the Firefox 141 instance on the device being used to write this post (same OS) does not include it) -The crash files in the .mozilla folder, meanwhile, consistently list a segfault at address 0x0. Any advice on diagnosing/solving this issue would be greatly appreciated. Let me know if there's any other information that would be helpful. If it would be more appropriate, I could report this through Mozilla's bugzilla instance, but given the issue seems to be very niche (Fedora's ABRT shows a total of 5 unique affected users in the last few days) I am unsure whether flagging this there would be appropriate.

தீர்வு தேர்ந்தெடுக்கப்பட்டது

Typical. Found the solution right after asking about it!

https://forum.manjaro.org/t/firefox-immediately-crashes-on-manjaro-kde-std-array-headerbarbuttontype-assert-gcc-15-2-1/180877

Seems to be a conflict between Firefox and KDE's customised window decorations (having close/minimise/maximise on both corners of the titlebar), and I have confirmed removing one of the decorations fixes the issue for me.

Leaving this here on the off-chance it might help anyone else, and for what it's worth I will look at reporting the bug to mozilla/KDE.

Read this answer in context 👍 0

All Replies (1)

தீர்வு தேர்ந்தெடுக்கப்பட்டது

Typical. Found the solution right after asking about it!

https://forum.manjaro.org/t/firefox-immediately-crashes-on-manjaro-kde-std-array-headerbarbuttontype-assert-gcc-15-2-1/180877

Seems to be a conflict between Firefox and KDE's customised window decorations (having close/minimise/maximise on both corners of the titlebar), and I have confirmed removing one of the decorations fixes the issue for me.

Leaving this here on the off-chance it might help anyone else, and for what it's worth I will look at reporting the bug to mozilla/KDE.

Helpful?

கேள்வி எழுப்பு

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.