Closed
Bug 1907697
Opened 3 months ago
Closed 3 months ago
Firefox gets stuck at 100% CPU in CheckDowngrade when starting
Categories
(Firefox :: General, defect, P3)
Firefox
General
Tracking
()
RESOLVED
DUPLICATE
of bug 1881536
People
(Reporter: jrmuizel, Unassigned)
Details
My release Firefox gets stuck at 100% CPU when starting up.
29.00 s 100.0% 0 s XREMain::XRE_mainStartup(bool*)
29.00 s 100.0% 0 s CheckDowngrade(nsIFile*, nsINativeAppSupport*, nsIToolkitProfileService*, nsTString<char> const&)
29.00 s 100.0% 0 s nsWindowWatcher::OpenWindow(mozIDOMWindowProxy*, nsTSubstring<char> const&, nsTSubstring<char> const&, nsTSubstring<char> const&, nsISupports*, mozIDOMWindowProxy**)
29.00 s 100.0% 0 s nsWindowWatcher::OpenWindowInternal(mozIDOMWindowProxy*, nsTSubstring<char> const&, nsTSubstring<char> const&, nsTSubstring<char> const&, bool, bool, bool, nsIArray*, bool, bool, bool, nsPIWindowWatcher::PrintKind, nsDocShellLoadState*, mozilla::dom::BrowsingContext**)
28.97 s 99.8% 0 s mozilla::AppWindow::ShowModal()
28.97 s 99.8% 22.00 ms bool mozilla::SpinEventLoopUntil<(mozilla::ProcessFailureBehavior)1, mozilla::AppWindow::ShowModal()::$_0>(nsTSubstring<char> const&, mozilla::AppWindow::ShowModal()::$_0&&, nsIThread*)
27.40 s 94.4% 63.00 ms NS_ProcessNextEvent(nsIThread*, bool)
21.32 s 73.5% 47.00 ms nsThread::ProcessNextEvent(bool, bool*)
16.46 s 56.7% 68.00 ms non-virtual thunk to nsAppShell::OnProcessNextEvent(nsIThreadInternal*, bool)
8.64 s 29.8% 0 s nsAppShell::OnProcessNextEvent(nsIThreadInternal*, bool)
8.64 s 29.8% 0 s nsBaseAppShell::OnProcessNextEvent(nsIThreadInternal*, bool)
5.19 s 17.9% 0 s nsBaseAppShell::DoProcessNextNativeEvent(bool)
5.19 s 17.9% 55.00 ms nsAppShell::ProcessNextNativeEvent(bool)
2.68 s 9.2% 3.00 ms nsChildView::UpdateCurrentInputEventCount()
2.67 s 9.2% 7.00 ms nsChildView::GetCurrentInputEventCount()
1.79 s 6.1% 119.00 ms SLEventSourceCounterForEventType
1.67 s 5.7% 874.00 ms CGSEventSourceForID
795.00 ms 2.7% 795.00 ms CGSScoreboard
Comment 1•3 months ago
|
||
The fix for bug 1881536 should have taken care of this.
Reporter | ||
Comment 2•3 months ago
|
||
Manually updating Firefox to 128 did fix this.
Updated•3 months ago
|
Status: NEW → RESOLVED
Closed: 3 months ago
Duplicate of bug: 1881536
Flags: needinfo?(eitan)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•