Closed Bug 1839248 Opened 2 years ago Closed 2 years ago

Tab crashes constantly on Google Image Search

Categories

(Firefox :: Tabbed Browser, defect)

Firefox 114
defect

Tracking

()

RESOLVED DUPLICATE of bug 1839669

People

(Reporter: tvi, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/114.0

Steps to reproduce:

I do a plain vanilla search on Google, I switch over to see what images are associated with the search terms.

Actual results:

Page begins to render, then the tab crashes. Trying to restore tab keeps causing crash.
Other user has had the same issue, cf. https://support.google.com/websearch/thread/221293972/google-images-constantly-crashing?hl=en

Expected results:

Page should have rendered with the images related to the search terms.

Addendum: Setting media.hardware-video-decoding.enabled to false in about:config seems to resolve the issue for the time being. What's strange is that it's a image search result page, not a video playback or search result page. Nothing out of the ordinary when using Web Console to see if anything stands out.

The Bugbug bot thinks this bug should belong to the 'Firefox::Tabbed Browser' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Tabbed Browser

(In reply to Teo V. from comment #1)

Addendum: Setting media.hardware-video-decoding.enabled to false in about:config seems to resolve the issue for the time being. What's strange is that it's a image search result page, not a video playback or search result page. Nothing out of the ordinary when using Web Console to see if anything stands out.

After working for a day, it suddenly ceased working again, so not a solution it seems.

Additional testing done, problem persists even in troubleshooting mode.

Hello, thank you for the bug report!
Unfortunately I could not reproduce the tab crash. Would you be so kind as to answer a few questions so we can investigate this further?

Thank you.

Flags: needinfo?(tvi)

By request, raw data for about:config.

Flags: needinfo?(tvi)

(In reply to Ardelean Oana, Desktop QA from comment #5)

Hello, thank you for the bug report!
Unfortunately I could not reproduce the tab crash. Would you be so kind as to answer a few questions so we can investigate this further?

(In reply to Ardelean Oana, Desktop QA from comment #5)

Hello, thank you for the bug report!
Unfortunately I could not reproduce the tab crash.

Here is some more information you might find useful. I could only reproduce the tab crash on my old Fedora 27 system, with Firefox builds from Mozilla itself. Any Firefox I could find had this issue, including Firefoxes packaged up in AppImage and similar systems, and they had this issue also on fresh brand new profiles running in troubleshooting mode.

But on my other systems, Fedora 37,38, I did not have this problem.

Also, if I downloaded the last Firefox that Fedora 27 offered (ancient Firefox 63!) it worked fine.

It appears to be that the problem may only occur with older Linux systems that try to run a newer Firefox. Some kind of api changes that didn't really matter until Google did whatever it did a few days ago with its Images pages.

Teo V could you report on what kernel, clib, etc versions you have? Maybe we just have to upgrade.

I'm running an up-to-date Debian 10, and latest FF - 114.0.2 (64-bit).
LIBC is libc6: 2.28-10

If it was something system-wide because the distro isn't the latest Debian, it would affect more than just one website. Like the only web site Tab crashes on is google images...

Added tests performed at this juncture is trying with and without uBlock Origin, same result regardless if site whitelisted.

(In reply to Teo V. from comment #9)

If it was something system-wide because the distro isn't the latest Debian, it would affect more than just one website. Like the only web site Tab crashes on is google images...

I don't think that is necessarily true. I think it can be a rare confluence of some strange html typical on the google image page, and some obscure behavior in some versions of some libraries that Firefox uses, that could create a problem. It could be that the page causes Firefox to issue some invalid api call (that Firefox should not have) and which most libraries do something innocuous with but some libraries object to.

So I suspect you and I have some libraries somewhere that don't deal with this call nicely, but most libraries do, and the specific call that exposes this fact did not exist until google changed its images page in some way very recently. But the specific library exposing this is not used by many; otherwise it is hard to explain why there are so few complaints about it. That's what I find interesting (and annoying).

What are you doing in the meantime? I switched to using Duck Duck Go. I don't think its search is at good as Googles unfortunately. I don't want to switch away from Mozilla, preferring their overall philosophy.

Oops, it also just occurred to me that when I did not duplicate the errors on more recent installations, that those installations are all running Wayland not X11. I wonder if that could be the difference, and not the age of the libraries (since yours are not that old).

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Duplicate of bug: 1839669
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: