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.
I for sure have a problem. But it basically boils down to remove your profile, which is not an option. I did report the issue number of times and always got “do a refresh”, which I always do and it always doesn’t help. Even made a video for them, since it doesn’t sound believable. This is on my X1 Carbon, which has M.2 drive. On my desktop with, at the time, HDD it was this slow.
At this point am only using Firefox out of spite so everyone doesn’t end up on Chrome since I remember what it was like for one company to have a huge monopoly. But I’d switch in a blink of an eye otherwise.
It’s not every day. My computer doesn’t get rebooted that often, maybe once in a month or two. So I got use to waiting that one time. But in general yes, I don’t want another profile as this one is synchronized with other devices and has all kinds of things I’d have to redo to fix an issue that shouldn’t exist in the first place.
DNS is not to blame here since Chrome and other applications work perfectly fine. Firefox in question is Developer Edition, so it’s bleeding edge new. And it’s not Debian because everything works fine until I sync my profile, then things slow down.
I know, mine starts like that on second start. First one always takes a while. After upgrade to SSH and M.2 it is faster but still not immediate like yours. And it’s not even a slow and outdated machine.
Sure it’s not a total beast, but still 12 cores and 32GB of RAM with decently fast SSD.
Nope, Debian Testing on machine with 12 cores and 32GB of RAM and 3GB/s M.2 drive.
And my systemd-analyze says graphical.target reached after 5.690s in userspace. Most of which is network manager waiting for online status, mounting filesystems, and timesyncd 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
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.
Opens just as quickly as any other program for me.
Either your boot time is like 0.05 seconds or you have a problem.
I for sure have a problem. But it basically boils down to remove your profile, which is not an option. I did report the issue number of times and always got “do a refresh”, which I always do and it always doesn’t help. Even made a video for them, since it doesn’t sound believable. This is on my X1 Carbon, which has M.2 drive. On my desktop with, at the time, HDD it was this slow.
At this point am only using Firefox out of spite so everyone doesn’t end up on Chrome since I remember what it was like for one company to have a huge monopoly. But I’d switch in a blink of an eye otherwise.
So suffering through atrocious load times every day is more palatable than just setting up a new profile?
It’s not every day. My computer doesn’t get rebooted that often, maybe once in a month or two. So I got use to waiting that one time. But in general yes, I don’t want another profile as this one is synchronized with other devices and has all kinds of things I’d have to redo to fix an issue that shouldn’t exist in the first place.
Here is an alternative Piped link(s):
Even made a video
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.
Then something is fishy with your install. Maybe something to do with the DNS or the Firefox version you’re using, or maybe just Debian.
DNS is not to blame here since Chrome and other applications work perfectly fine. Firefox in question is Developer Edition, so it’s bleeding edge new. And it’s not Debian because everything works fine until I sync my profile, then things slow down.
That’s wack. I’ve never seen Firefox that take long to open. Here’s a video of it opening in a VM running Ubuntu 22.04: https://streamable.com/aqkftv
I know, mine starts like that on second start. First one always takes a while. After upgrade to SSH and M.2 it is faster but still not immediate like yours. And it’s not even a slow and outdated machine.
Sure it’s not a total beast, but still 12 cores and 32GB of RAM with decently fast SSD.
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-analyzesaysgraphical.target reached after 5.690s in userspace.Most of which is network manager waiting for online status, mounting filesystems, andtimesyncdwaiting 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?