Open Bug 1259805 Opened 10 years ago Updated 2 years ago

Firefox 45 freezes when confirming flight changes on easyjet.com

Categories

(Core :: General, defect)

Product:
Core
Component:
General
Version:
45 Branch
Platform:
All
Unspecified
Type:
defect

Tracking

()

People

(Reporter: LpSolit, Unassigned)

Details

I tested with Firefox 45 on Linux, Mac and Windows 10 (different machines, no VM). In all cases, Firefox freezes when changing flight parameters in easyjet.com. It works correctly with Edge on Windows 10. I cannot give much information besides that the CPU reached 100% and I had to manually kill the process. Steps to reproduce: - Login to your easyjet.com account. - Select a flight and ask to change it (I needed to delay my departure). - Select a new flight, click "Continue". Firefox freezes. And yes, I tried with all modules deactivated. :)
Severity: normal → S3

Hi Andrei, could you please help with finding someone to verify if this is reproducible? If not, let's close it.

Flags: needinfo?(avaida)

I have managed to reproduce one browser freeze on the 1st try in a total of 10 tries on Ubuntu 22 with Firefox 127.0.2. This freeze happened after clicking the "Change selection" link, in order to choose another departure flight, on the "Fares" screen (after "Pick flights" screen). The session did not recover from the freeze and the session had to be quit and restarted; no crash report was logged. This freeze could not be reproduced again.

This issue could not be reproduced again in either Ubuntu, Windows or MacOS in many tries using the lastest Release v128.0, Beta v129.0b1 and Nightly v130.0a1.

I have also attempted to reproduce it in an old Firefox v45, but clicking the "Sign in" button had no effect. I was not ale to sign in at all, despite the errors encountered on all browsers, described below.

I encountered some errors (that appeared to be website issues) when logging in. An error kept being displayed when attempting to log into the account; I had to attempt to log in repeatedly to succeed. Error message:
"An error occurred
We're very sorry but something has gone wrong. Please try again or get in contact with us if this issue continues to occur.
You can view our local telephone numbers on our contact us page
Error correlation number: F20CBBAD-5B50-F157-1F28-7605CCB48F72"

In conclusion, it appears that the original freeze could not be reproduced, except for 1 random occurrence on Linux that happened at a slightly different point in the flow.

Flags: needinfo?(avaida)
You need to log in before you can comment on or make changes to this bug.