211–220 of 361 posts
Earlier quoted context omitted.
Much of the recent breakage was to introduce essential features that users have been loudly asking for for years, such as multi-process support and content processes in a security sandbox. If you're intentionally running very old versions which by now have published exploits, then I can see that these are not things you would consider important.
Progress at what cost? Does maintaining security have to also mean breaking the systems that pay my bills?
Earlier quoted context omitted.
IIRC per-tab e10s already exists, just isn't enabled by default yet because it has some rough edges. The Rust part of your comment is irrelevant. There is Rust code shipping in Firefox, but nowhere near the amount needed for observable changes in behavior. Work is being done to put larger components in but nothing is shipping yet. Also, IME most crashes are asserts (in all browsers) and that's not a problem Rust fixe…
If process-per-tab is enabled, can each tab crash separately, or does the whole browser still have to go down?
Disclaimer: I dual boot (camp) windows 7 on my mac.
Earlier quoted context omitted.
IIRC per-tab e10s already exists, just isn't enabled by default yet because it has some rough edges. The Rust part of your comment is irrelevant. There is Rust code shipping in Firefox, but nowhere near the amount needed for observable changes in behavior. Work is being done to put larger components in but nothing is shipping yet. Also, IME most crashes are asserts (in all browsers) and that's not a problem Rust fixe…
If process-per-tab is enabled, can each tab crash separately, or does the whole browser still have to go down?
Note that this means that tabs will share content processes, so a crash in one tab may crash a few others. You can reduce this by ramping up the number of processes, though that can lead to bloat.
No idea how stable this is right now. For me, on Dev Edition with regular multiprocess mode enabled, things work fine and I don't get crashes.
Earlier quoted context omitted.
I use https://addons.mozilla.org/en-US/firefox/addon/cmd-q-catcher... to force me to hit it twice to actually quit. Dunno if it works on platforms besides Mac though.
Thanks, I do that all the time. Installed.
Earlier quoted context omitted.
Launchpad is such a shitty website, aimed at Ubuntu and only Ubuntu, links to source code or more information are nowhere to be found... Searching on Github, this seems to be it. Turns out, there's releases for Arch, Debian, etc. and it's even in the repositories. No need to add a ppa. https://github.com/graysky2/profile-sync-daemon For Debian and co: $ apt-cache show profile-sync-daemon $ sudo apt-get install profil…
I checked the Activity Monitor on OS X to see if it's the same and if I should do something. It's quite surprising: bird 11,38 GB 119,8 MB kernel_task 8,82 GB 23,0 MB launchd 8,46 GB 77,7 MB revisiond 8,35 GB 105,8 MB Tweetbot 3,01 GB 50,2 MB Safari 879,6 MB 10,0 MB mds_stores 726,2 MB 570,1 MB systemstatsd 695,0 MB 775,0 MB nsurlstorag 685,3 MB 9,5 MB Google Chrom 681,4 MB 303,5 MB iTerm2 653,7 MB 1,6 GB cfprefsd 50…
Earlier quoted context omitted.
Who really cares about restoring browser state? Maybe I lose part of an HN or Facebook post I'd been writing, but that's it. The feature should be opt-in, IMHO.
I certainly care about it, although it's possible that my 50-odd browser tabs would be considered "clutter" by other people. I stopped using Edge because it only saves your tab session if you turn off the PC, not if you quit the browser. Mind you, for a while I ran Firefox using a RAMdisc for the profile simply because all that flushing makes a big negative impact on PC performance.
Chrome, on my system, is even more abusive. Watch the size of the .config/google-chrome directory and you'll see that it grows to multi-GB in the profile file. There is a Linux utility that takes care of all browsers' abuse of your ssd called profile sync daemon, PSD. It's available in the debian repo or [1] for Ubuntu or [2] for source. It uses `overlay` filesystem to direct all writes to ram and only syncs back to…
I guess doing something like this on Windows is too much to hope for, but does anyone know how to do this sort of thing on the Mac?
Chrome, on my system, is even more abusive. Watch the size of the .config/google-chrome directory and you'll see that it grows to multi-GB in the profile file. There is a Linux utility that takes care of all browsers' abuse of your ssd called profile sync daemon, PSD. It's available in the debian repo or [1] for Ubuntu or [2] for source. It uses `overlay` filesystem to direct all writes to ram and only syncs back to…