Open Bug 1888322 Opened 1 month ago Updated 8 days ago

Latest update crashes and cause processor loop crash.

Categories

(Core :: Performance, defect)

Product:
Core
Component:
Performance
Version:
Firefox 126
Type:
defect

Tracking

()

Status:
UNCONFIRMED
Project Flags:
Performance Impact ?

People

(Reporter: fusionor, Unassigned, NeedInfo)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36

Steps to reproduce:

Update popped up while using browser. When I clicked on it, it installs and then restarts but then it hangs showing blank browser with tab trying to form.

Actual results:

Once I close via task manager and click to start, warning pops up saying "Firefox is already running, but is not responding. The old Firefox process must be closed to open a new window." Pressing Close Firefox causes it pop back up again with the same message. Clicking Cancel closes the program. Task Manager shows 0% CPU usage and 45 MB Memory.

Expected results:

Update should had just updated and restarted browser.

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

Component: Untriaged → Application Update
Product: Firefox → Toolkit
Component: Application Update → Performance
Product: Toolkit → Core

This bug was moved into the Performance component.

:fusionor, could you make sure the following information is on this bug?

  • For slowness or high CPU usage, capture a profile with http://profiler.firefox.com/, upload it and share the link here.
  • For memory usage issues, capture a memory dump from about:memory and attach it to this bug.
  • Troubleshooting information: Go to about:support, click "Copy raw data to clipboard", paste it into a file, save it, and attach the file here.

If the requested information is already in the bug, please confirm it is recent.

Thank you.

Flags: needinfo?(fusionor)
Performance Impact: --- → ?
You need to log in before you can comment on or make changes to this bug.