Open Bug 1817580 Opened 2 years ago Updated 2 months ago

Opening first page after cold bool takes up to 3 minutes, 85% in mozilla::dom::LSObject::GetItem (W10)

Categories

(Core :: Storage: StorageManager, defect, P3)

Firefox 110
defect

Tracking

()

UNCONFIRMED

People

(Reporter: moukira45, Unassigned)

References

(Depends on 1 open bug)

Details

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

Steps to reproduce:

Boot into windows
Open Firefox
Open any web page

Actual results:

The page is loading for ~3 minutes
When checking the capture created by launching Firefox with MOZ_PROFILER_STARTUP=1, I can observe 85% of startup time under WebExtensions > mozilla::dom::LSObject::GetItem

Capure is here https://share.firefox.dev/3XFjiLN

Expected results:

Loading should not take more than a few seconds (other pages after the first one finished loading behave as expected)

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

Component: Untriaged → DOM: Core & HTML
Product: Firefox → Core
Component: DOM: Core & HTML → Storage: StorageManager

Could this be related to a data migration or archival?

Severity: -- → S3
Flags: needinfo?(jvarga)
Priority: -- → P3

I've had this problem for quite some time now, and only took time to report it now.
I don't remember precisely, but I feel this issue appeared progressively.

(In reply to Jari Jalkanen from comment #2)

Could this be related to a data migration or archival?

It's most likely related to slow temporary storage initialization when there are many origins in combination with slower hardware.

Depends on: 1671932
Flags: needinfo?(jvarga)

Update on this : this may indeed be related to slow storage hardware. My data are on an aging HDD, and I'm usually not cleaning my history and site data.
Made some cleanup last week, deleting all site data and cache + clearing history older than 6 months, and now the startup time is way faster.
Still, it is a bit weird to not be able to load a webpage until user data has been loaded.
But I guess the issue is solved for now on my side (until data accumulate again, or I switch to faster storage)

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