this post was submitted on 31 Oct 2023
498 points (98.4% liked)
Technology
58942 readers
3734 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Rendering was never a problem with FF, but it's good to see some progress on that front as well. Startup times are still atrocious. My whole OS can book 4 times over before Firefox decides it's the right time to start rendering something.
Damn, what are you using, WinME?
Nope, Debian Testing on machine with 12 cores and 32GB of RAM and 3GB/s M.2 drive.
And my
systemd-analyze
saysgraphical.target reached after 5.690s in userspace.
Most of which is network manager waiting for online status, mounting filesystems, andtimesyncd
waiting clock update.Sounds like you have a borked dbus or is using the GTK_USE_PORTAL env variable, 20 second timeouts are gtks standard way of dealing with something it doesn't like. Firefox should take < 1 second to start fresh and takes < 3s for me, restoring hundreds of tabs
Hm, interesting idea. Any suggestion how I can check/reset this?