81–90 of 361 posts
Earlier quoted context omitted.
Replace Browser Crash with: Accidentally pressing Ctrl-w And yes, there are browser crashes without Flash
Why should it save the whole page when it only needs to remember the URL? At most, maybe also any form data you have entered. Small enough to keep thousands of pages in memory.
The internet allows it to do that.
Basically chattr +i on a whole bunch of its files and databases, and everything's fine again...
The interesting question here is, why is the browser writing data to disk at this rate? If it's genuinely receiving new data at this rate, that's kind of concerning for those of us on capped/metered mobile connections. The original article mentions that cookies accounted for the bulk of the writes, which is distressing. If it's not, using incremental deltas is surely a no-brainer here?
Might be surprisingly hard or inefficient given that you're trying to capture "webpage state". Think about React sites etc.
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…
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 profile-sync-daemonEarlier quoted context omitted.
Some cheap drives (e.g. Crucial BX100) have an endurance rating of only about 40GB/day.
So even with a cheap drive, if you leave your browser open with tons of tabs, and the PC on 24/7, it'll still easily handle it? Real lifetimes are often a multitude of the endurance rating, BTW.
Maybe I am not understanding this right, but is this saying that Firefox will continually keep writing to the disk while idle? Does anyone know more about this? Why would this be needed to restore session/tabs? Seems like it should only write after a user action or if the open page writes to storage? Even if it was necessary to write continually while idle, how could it possibly consume so much data in such a short p…
This is very much the feature working as intended: Firefox captures webpage state every 15 seconds, so a crash, power outage, accidentally closing the browser etc will not result in data loss for the user. For storing the data persistently, it uses the persistent storage, i.e. your harddrive. For the HN crowd, that's going to be an SSD. The SSD can easily deal with the resulting write traffic with negligible effect on its lifetime - I have no idea why people even think this is an issue.
Seems like it should only write after a user action or if the open page writes to storage
Webpages can change their contents or state without user interaction.
Webpages are also big and bloated. Storing a little data, all the time, 24/7, adds up over time to a surprisingly large number.
Firefox really started to annoy me with its constant and needless updates a few months back; the tipping point being breaking almost all legacy extensions (in 46, I believe). This totally broke the Zend Debugger extension, the only way forward would be to totally change my development environment. I'm 38 and now, and apparently well beyond the days when the "new and shiny" hold value. These days I just want stability and reliability.
Firefox keeps charging forward and, as far as I can tell, has brought nothing to the table except new security issues and breaking that which once worked.
I haven't updated since 41 and you know what, it's nearly perfect. It's fast, does what I need it to do, and just plain old works.
Firefox appears to have become a perfect example of developing for the sake of.
Earlier quoted context omitted.
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.
You're in good shape. I'm at 337 tabs. ;-)
Chrome Extension: https://chrome.google.com/webstore/detail/tabist/hdjegjggiog...
Firefox Extension: https://addons.mozilla.org/en-US/firefox/addon/tabist/
source code: https://github.com/fiveNinePlusR/tabist
Let me know if you find it useful or have any suggestions.
In Linux where should this be written? Inside the home folder? Maybe moving this folder to a HDD should suffice.
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…