Bug 1179381

Summary: Firefox 82 crashes on some pages
Product: [openSUSE] openSUSE Tumbleweed Reporter: Pavel Šimerda <pavlix>
Component: FirefoxAssignee: Mozilla Bugs <mozilla-bugs>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: gfx-bugs, pavlix, ptesarik
Version: Current   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Pavel Šimerda 2020-11-29 14:37:02 UTC
I have just fully upgraded Tumbleweed. Firefox tabs now crash on StackOverflow, LinkedIn, Reddit and probably much more. The whole Firefox instance crashes on about:support. It might be related to Wayland.

An interesting thing is:

/usr/bin/firefox crashes.

/usr/lib64/firefox/firefox doesn't crash.

Therefore it must probably be somewhat related to the environment. The following error is in the console (only when a tab/instance) crashes.

Can't find symbol 'eglSwapBuffersWithDamageEXT'.

In both cases I removed WAYLAND related ENV variables including WAYLAND_DISPLAY and MOZ_ENABLE_WAYLAND but not SWAYSOCK.
Comment 1 Pavel Šimerda 2020-11-29 14:41:17 UTC
It must be somewhat related to GL.

$ unset MOZ_ENABLE_WAYLAND
$ /usr/lib64/firefox/firefox

The above sequence gets rid of the crashes. Not wayland enabled. Not /usr/bin/firefox.
Comment 2 Petr Tesařík 2020-11-30 14:03:59 UTC
I wonder if this is somehow related to bug 1179298. Do you have Chromium installed on your system?
Comment 3 Pavel Šimerda 2020-12-10 14:54:45 UTC
(In reply to Petr Tesařík from comment #2)
> I wonder if this is somehow related to bug 1179298. Do you have Chromium
> installed on your system?

I have Chromium installed. That bug report unfortunately doesn't have instructions to check & workaround.
Comment 4 Stefan Dirsch 2021-01-04 11:31:45 UTC
Not really. :-( You'll need to update chromium. And make sure the change 

- Remove erroneous call to ldconfig which causes Firefox crashes (boo#1179298)

is in. I believe we can close this as duplicate.  Updates are available for openSUSE since end of November 2020.

That has been the fix.

--- chromium.spec (revision 1502)
+++ chromium.spec (revision 1503)
@@ -795,12 +795,10 @@
 %post
 %icon_theme_cache_post
 %desktop_database_post
-/sbin/ldconfig %{_libdir}/chromium
 
 %postun
 %icon_theme_cache_postun
 %desktop_database_postun
-/sbin/ldconfig %{_libdir}/chromium
 
 %files
 %license LICENSE

*** This bug has been marked as a duplicate of bug 1179298 ***
Comment 5 Pavel Šimerda 2021-01-05 11:34:42 UTC
I confirm that I no longer see this issue in updated Tumbleweed.

> Updates are available for openSUSE since end of November 2020.

However, this bug was reported at the end of November using a fully updated and restarted Tumbleweed! How is that possible?
Comment 6 Stefan Dirsch 2021-01-05 12:07:23 UTC
You reported it one day before fixed updates for openSUSE Leap were available. I don't know when it has been fixed for Tumbleweed.