Open Bug 2063567 Opened 2 months ago Updated 3 hours ago

shutting down firefox browser sometimes leaves the process still running in the background for several seconds, causing the new browser startup to start slowly and with error message

Categories

(Core :: Performance: General, defect)

Product:
Core
Component:
Performance: General
Version:
Firefox 153
Type:
defect

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: u793744, Unassigned, NeedInfo)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:153.0) Gecko/20100101 Firefox/153.0

Steps to reproduce:

I close the browser from the X in the upper right corner and immediately try to open the browser again.

Actual results:

Sometimes this causes the new browser startup to take several seconds and sometimes causing it to start full white non-responsive and with an error message popup saying that Firefox is still running and needs to be shut down.

Expected results:

The Firefox background processes shut down immediately with the browser and new browser session is able to open up without a delay or unresponsiveness.

The Bugbug bot thinks this bug should belong to the 'Core::Networking' component, but is not confident enough to move the bug to that component.

Component: Untriaged → General
Component: General → Performance: General
Product: Firefox → Core

This bug was moved into the Performance: General component.

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

  • For slowness or high CPU usage, capture a profile with https://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. Please consider moving this issue to the Performance: Memory component.
  • 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?(ollinzalando)

Redirect a needinfo that is pending on an inactive user to the triage owner.
:bas.schouten, since the bug has recent activity, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(u793744) → needinfo?(bas)

I'm on the Firefox Developer release (currently 160.0b1).
I've been encountering this issue sporadically for the past few months (I would guesstimate since around ~v154)

I've enabled the profiler and captured and shared two logs, one from the session that didn't shutdown, and the second from the following session that displayed the error dialog at startup:

  1. log from delayed shutdown
  2. attempt to open firefox -> error dialog "firefox is already running and needs to be closed" -> click close
  3. log from startup that triggered error dialog

Bug 2040781 appears to be related or perhaps the same issue
Bug 2074073 could also have been the same issue (since the issue only manifests when you quickly open a new window after having shut one down, the reporter may have been led to believe that the issue was resolved simply because they didn't repeat the conditions needed to encounter it)

I had the issue again today.
I haven't shared the profiler log because it's rather large, but I've saved it if you'd like to see it.

I did load both logs (of the sessions that left firefox running) to profiler.firefox.com, trying to see if I could spot any commonalities.

One thing I noticed is that in both cases the network thread of the Parent process ends with a request to: https://incoming.telemetry.mozilla.org/submit/firefox-desktop/use-counters/1/... and the status of that request in both cases was "Waiting for response"

fwiw, I looked at the profiler logs that were shared for Bug 2040781 (which I suspect may be the same issue as this bug)

All 4 of the logs shared over there, ended with Parent process requests to https://incoming.telemetry.mozilla.org/submit/... --- two had "Waiting for response" status and two had "Response Received" status, but those took awhile.

(In reply to grundtworks from comment #6)
oops, meant to link to this comment Bug 2040781

In comment #4, I mentioned that I had only recenlty started encountering this behavior.
Well now that I have a suspicion of what may be causing it, it occurred to me that it was also around the time I enabled the "Send technical and interaction data to Mozilla" setting.
So if it is in fact that setting that causes this behavior, I'm fine with it. I don't consider that a bug.

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