1803841 - System freezes each time Firefox is used to browse to Prime video/Categories/Movies on amazon.com

Status: RESOLVED INACTIVE

(Core :: Performance, defect)

Description

[StephenP]

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

Steps to reproduce:

STEPS TO REPRODUCE

1. Open amazon.com in Firefox
2. Browse to Prime Video/ Categories / Movies

Operating System: Fedora Linux 36
KDE Plasma Version: 5.26.3
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
Kernel Version: 6.0.10-200.fc36.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz
Memory: 15.6 GiB of RAM
Graphics Processor: AMD Radeon R9 380 Series
Manufacturer: Dell Inc.
Product Name: XPS 8500

Actual results:

Keyboard and mouse disabled / screen freeze
try to ssh from another computer / very slow response
once logged in to affected computer try to execute shutdown -h now
No response. ps and other commands are slow and kill commands ineffective
The only recourse is to shut off the computer manually.
ADDITIONAL INFORMATION
This happens everytime and only recently
The same crash happens on my other computer with the same hardware and configuration.
It does not occur using Chrome.

Expected results:

One should be able to navigate to the page on the site without encountering a system freeze.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

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

Comment 2

[Mike Conley (:mconley) (:⚙️)]

If the keyboard and mouse are unresponsive, something is probably going wrong at the system level. I think we need more information before we can get a clear sense of what's going wrong.

If you can reproduce this reliably, I think the next step is to try to collect a stack for where Firefox is when it locks up like this. I know that the system is really slow to respond, but if you're able, the following information would be really helpful:

1. Before triggering the bug, make note of the pid of the main Firefox process
2. Trigger the bug
3. Either remotely via SSH or on the same machine, attach to Firefox when it's locked up using sudo gdb -p <pid> where <pid> is the PID of the process that you gathered in (1).
4. Once gdb attaches (if the system is really slow, this may take a while...), type in bt and press Enter to collect a backtrace
5. Copy that backtrace, and then paste into this bug report.

That might help give us a sense of where Firefox is stuck, at least. We might need more information if the whole system is stuck doing something, but we can cross that bridge when we get there.

Comment 3

[Dave Hunt [:davehunt] [he/him] ⌚BST]

With no answer from the reporter, we don’t have enough data to reproduce and/or fix this issue. Please reopen or file a new bug with more information if you see it again. Details of our performance triage process can be found at https://wiki.mozilla.org/Performance/Triage.