Closed Bug 1841777 Opened 2 years ago Closed 2 years ago

Google Images search reproducibly causes tab crash

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Version:
Firefox 115
Platform:
x86_64
Linux
Type:
defect

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: rjvbertin, Unassigned)

Details

Crash Data

+++ This bug was initially created as a clone of Bug #1839669 +++

From what I understand the google image search crash should be fixed in Firefox 115 but I'm still getting it in 115.0b9 .

Running Ubuntu 14.04LTS5 with lots of self-updated components and a 4.19 kernel.

:rjvbertin, if you think that's a regression, could you try to find a regression range using for example mozregression?

I don't think it's a regression, it is more as if the fix for #1839669 isn't included or not sufficient.

I had the Google Images crash with 114.0b6 and upgraded from there to 115.0b9 which (for me) shows up as the newest version in the Dev. Edition channel. FWIW, #1839669 was created for 115.0b7 so maybe my assumption is wrong that 115.0b9 is a beta release that is newer than the 115.0 release version?

Yeah, 115.0b9 doesn't have the fix. It was uplifted directly to the RC in bug 1839669 comment 73. It's right tho that https://www.mozilla.org/en-US/firefox/channel/desktop/#beta downloads a 115.0b9 still... Do you know what's up with that?

Flags: needinfo?(ryanvm)

116.0b1 ships today (Long week end due to July 4 impact to the schedule), see https://whattrainisitnow.com/release/?version=116

Flags: needinfo?(ryanvm)

115.0b9 is the latest beta build. 116.0b1 hasn't shipped yet, and even when it does, bug 1840878 means the download link will stay at 115.0b9 until (probably) 116.0b2.

OK, so this ticket is spurious.

Evidently I have no idea why the download page or the internal updater still pushes/pulls 115.0b9 and I'd appreciate it if someone in the know could give an estimate when a version with the fix will be available!

(I don't want incessant update reminders so I use the distribution/policies.json trick to prevent those and just do periodic update checks myself. Quite annoying BTW that I can no longer even check for updates in a secondary browser instance without quitting my main session!)

The internal updater should offer the 115.0 release build.

Even if you're on the Dev. Edition channel? It definitely doesn't offer 115.0 for me at the moment.

Ah, yes, for dev edition 115.0b9 is the latest.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME

(In reply to Julien Cristau [:jcristau] from comment #9)

Ah, yes, for dev edition 115.0b9 is the latest.

Hrmf, so dev edition can actually be behind the release version? That seems off, somehow!

(In reply to René Bertin from comment #6)

OK, so this ticket is spurious.

Evidently I have no idea why the download page or the internal updater still pushes/pulls 115.0b9 and I'd appreciate it if someone in the know could give an estimate when a version with the fix will be available!

(I don't want incessant update reminders so I use the distribution/policies.json trick to prevent those and just do periodic update checks myself. Quite annoying BTW that I can no longer even check for updates in a secondary browser instance without quitting my main session!)

You can just go to https://whattrainisitnow.com and put your mouse over the beta version number, a tooltip will appear with the current beta sent to users.

116.0b1 is currently in QA, we should ship it later today.

DevEdition is a beta, it follows the beta schedule, not the release schedule and as such, does not have release candidates. It will update to 116.0b1 later today as well.

(In reply to Pascal Chevrel:pascalc from comment #11)

DevEdition is a beta, it follows the beta schedule, not the release schedule and as such, does not have release candidates. It will update to 116.0b1 later today as well.

But isn't 115.0 also the 1st beta for 115.1 (or whatever you call the next version)? ;)

Due to the way our branching for releases works, the current situation is the expected result. DevEdition is frozen during RC week until the new release train rides from Nightly to Beta. Given that, it sounds like everything is working as intended/expected here. If you're still crashing after picking up DevEdition 116 builds going out starting today, feel free to reopen the bug.

Resolution: WORKSFORME → INVALID

Updated and fixed.

(As usual I did have to restore a number of windows/tabs manually that FF didn't cared to reopen automatically >:( )

You need to log in before you can comment on or make changes to this bug.