Earlier quoted context omitted.
I currently have 2014 tabs in my session (almost all unloaded, using around 2GB of ram that I wouldn't use otherwise). I had 1600 tabs a few days ago. They are links I clicked on in other apps or browsed to over the past few months. When I get a chance to plow through a few dozen/hundred of these tabs I can read/view them and close them very quickly. Notice all the UI stuff I don't have to do: I never had to perform…
In terms of UI stuff, how do you find a tab among a thousand? When the tab page title shrinks and all I see is favicon, I feel lost.
Multiprocess Firefox
131–140 of 171 posts
Re: Multiprocess Firefox
#132Earlier quoted context omitted.
> The way I use Firefox is that having 50 or more tabs open is normal for me I've never understood this. Isn't that what bookmarks are for?
I currently have 2014 tabs in my session (almost all unloaded, using around 2GB of ram that I wouldn't use otherwise). I had 1600 tabs a few days ago. They are links I clicked on in other apps or browsed to over the past few months. When I get a chance to plow through a few dozen/hundred of these tabs I can read/view them and close them very quickly. Notice all the UI stuff I don't have to do: I never had to perform…
Re: Multiprocess Firefox
#133Earlier quoted context omitted.
I had the same experience though I have to admit that some things in Firefox are better these days, like checking where an event comes from, going really deep into objects, referencing other objects, comparing rather big objects. The only thing I really miss is a view WebSocket frames. In many other cases I ended up preferring Firefox Dev Tools which I think while a bit harder to get into are more powerful. But that…
The only thing I'm missing in either browser is the ability to ignore jQuery as I'm debugging. Stepping in and out of jQuery (and other libraries like underscore) is a pain.
You can also use the developer toolbar to run a command like `dbg blackbox --glob *-min.js` etc. to blackbox a bunch of stuff at once.
https://developer.mozilla.org/en-US/docs/Tools/Debugger/How_...
Re: Multiprocess Firefox
#134Now if I can only fix the wobbly address bar that changes size depending on Back/Forward availability.
Those sorts of fit-and-finish bugs really bother me, and I'd love to figure out how we can fix that one for you.
Re: Multiprocess Firefox
#135Earlier quoted context omitted.
I had the same experience though I have to admit that some things in Firefox are better these days, like checking where an event comes from, going really deep into objects, referencing other objects, comparing rather big objects. The only thing I really miss is a view WebSocket frames. In many other cases I ended up preferring Firefox Dev Tools which I think while a bit harder to get into are more powerful. But that…
The only thing I'm missing in either browser is the ability to ignore jQuery as I'm debugging. Stepping in and out of jQuery (and other libraries like underscore) is a pain.
Re: Multiprocess Firefox
#136From the experience I've had with Chrome, I would say that process per tab is overhead. Sure, there are some benefits from having a few processes that are managing different parts of the system, but not hundreds of processes just for browsing. The way I use Firefox is that having 50 or more tabs open is normal for me, sometimes there are even hundreds of them. Currently Firefox works great and although there are some…
"There are multiple competing factors when it comes to choosing the right number of processes. - For security, more processes is better; one per tab is probably ideal. - For crash protection, ditto. - For responsiveness, one process per CPU core is probably best. - For memory usage, one process is probably best." as a dev wrote in the mailing list: https://groups.google.com/forum/#!topic/mozilla.dev.platform... For v…
Here is the original paper: https://crypto.stanford.edu/cs155/papers/sfi.pdf
Re: Multiprocess Firefox
#137Please please test battery life impact while implementing the Multi-process stuff. I had to move away from Chrome just on the battery life issue. I suspect (but cannot conclusively prove) that the multi-process crap that Chrome has just drains your battery much faster. And yes I am perfectly aware of the supposed fix in Chrome for the battery killing bug.
Safari is multi-process and it has the best battery life.
Re: Multiprocess Firefox
#138From the experience I've had with Chrome, I would say that process per tab is overhead. Sure, there are some benefits from having a few processes that are managing different parts of the system, but not hundreds of processes just for browsing. The way I use Firefox is that having 50 or more tabs open is normal for me, sometimes there are even hundreds of them. Currently Firefox works great and although there are some…
Re: Multiprocess Firefox
#139Earlier quoted context omitted.
ctrl-shift-e should open a canvas like area where you can group tabs. Similar to a file folder, I prefer it to bookmarks
Interesting, but seems to be very basic. I still prefer using a wm. I can use different layouts, group windows into hierarchies, display them side by side, take advantage of tiling, use workspaces and have configurable keys for each of these actions. You know, functions that a wm is built for. And I can always switch to a different wm altogether if I'm not comfortable.
Obviously you can easily achieve the same thing in separate windows as well, so ultimately I suppose it doesn't make a huge difference, but it's the way I find makes for the biggest difference in separating workspaces.
Re: Multiprocess Firefox
#140Earlier quoted context omitted.
I currently have 2014 tabs in my session (almost all unloaded, using around 2GB of ram that I wouldn't use otherwise). I had 1600 tabs a few days ago. They are links I clicked on in other apps or browsed to over the past few months. When I get a chance to plow through a few dozen/hundred of these tabs I can read/view them and close them very quickly. Notice all the UI stuff I don't have to do: I never had to perform…
What extension do you use to unload your tabs? Or keep them unloaded, not sure of your workflow in that regard.