And now the dark theme also applies to address bar and hamburger menu which is nice bonus.
UPDATE: So far, so good! Multiple account containers open, lots of different websites that usually would cause problems, and so far it's running fine! Also had Ghostery left installed and uninstalled that as well as it also hogged CPU time on Chrome, so that may have had an effect. All in all, think this is g'bye, Chrome.
I currently use Chrome's account profiles for this, so I have a desktop where my work profile lives and a desktop where my personal profile lives, and this makes links followed from other applications Just Work so long as I'm on the right desktop for them. I could probably get used to a slightly more awkward workflow, and the history being annoyingly shared between them, but...
EDIT: ah, well, I found the relevant github issue. Looks like there's years of arguing yet to go! https://github.com/mozilla/multi-account-containers/issues/3...
No keyboard shortcuts to speak of.
The problem is not having just one instance open all the links. It seems it might be possible to hack around that by writing your own url handler for your os, then dispatching to the correct instance. (https://superuser.com/questions/119014/how-to-remotely-open-...)
But, as you say, the problem with that is that it doesn't handle opening links correctly.
I could see if I could write a URL handler that queries the window manager to find the last Firefox window that had focus on the current desktop (probably possible, but I'm unfamiliar with that domain)... or I could view Firefox not supporting this natively as a sign that it doesn't think my use case is very important, and stick with a browser that works without jumping through hoops.
It's not that I'm averse to putting some work in, per se -- I'm now in the middle of poking at writing a Firefox add-on to see if I can fix my complaints about insufficiently sticky containers -- it's just that writing my own OS url handler is a bit too hacky for my tastes.
https://github.com/kemayo/firefox-sticky-containers
I'm currently seeing whether #webextensions on irc.mozilla.org feels like ripping it to shreds, but I'll put it up on AMO after that's done.
The problem was fixed, but all the text looks bad now.
Yes I'm one of "those" people. I hoard tabs like they're going out of style.
I have seen it spike to 400% a few times in activity monitor.
As to what I'm doing, open up say lobsters, click on all the tabs that look interesting, forget them for a day, repeat. End of the week have a look see at things.
https://addons.mozilla.org/en-US/firefox/addon/umatrix/
Firefox has built-in tracking protection that can be enabled in non-private windows too.
After weeks of effort, a team mate finally figured out that a default noop function param, eg function blah( param = () => {} ), was never being gc’d. Wut?!
But yes, in general tracking down leaks in JS is a huge pain...
There are some browser-specific tools that will do something like that out-of-band (e.g. in Firefox about:memory has a "Save GC & CC logs" option that outputs data about what the GC and cycle collector heap graphs look like). But interpreting those graphs is not easy, sadly.
More information about the technique can be found in a PLDI paper (which I presented last week :D ), which I tried to write clearly so that it is accessible to a technical audience (i.e., non-academics) [1].
[0] http://bleak-detector.org/
[1] https://dl.acm.org/citation.cfm?doid=3192366.3192376 (shouldn't be paywalled, but if it is, it's also available at [0])
If it would, please let me know at bzbarsky at mit dot edu.
If not, would you be willing to use a Firefox nightly and follow the steps at https://developer.mozilla.org/en-US/docs/Mozilla/Performance... then send me a link to the profile that gets generated?
I agree that if it's a leak on the Ubiquiti side they would be best placed to deal with that aspect, but there might be things we can do better on the Firefox side to handle pages leaking too...
On the other hand, everything is blurry. I've searched to no end, and haven't found a solution. It looks like third-party apps used to when the rMBP was first released and apps that performed their own text rendering hadn't yet been updated to support it.
Any ideas?
Edit: I have no idea how this was even ever set in the first place, but a sibling comment mentioned the "Open in Low Resolution" flag that can be set on a binary, and it was enabled for Firefox on my machine. Either I set this manually trying to solve the performance issues (and somehow this setting persisted across uninstalls), or Firefox ships with this flag set. Unchecking it fixed the blurriness, and hopefully didn't bring back the performance problems.
Google Maps, unfortunately, still made my CPU temp spike 30C+ as soon as I opened it. I use Maps a lot, so this is still a deal breaker for me.
Interesting thing I've noticed: If you don't use chat much and just want the video, try using Twitch's "pop-out" player that opens in its own window- for me this uses far less CPU (even in Chrome)
Chrome's "switch to fullscreen" transition on twitch for me is super laggy though, and I haven't been able to solve that one (Firefox switches to fullscreen smoothly).
I have both normal FF and nightly FF. Before nightly getting the dark hamburger menu I'd never thought much of it. After nightly got the dark menu, now on normal FF I can't help but notice it every time I open the menu, and it annoys me to no end. Funny how these things work.
So no, I wouldn't call this a great release.
Where's that in the menus?
This is the page I always test for Firefox CPU usage: https://flypaper.soundfly.com/
I don't visit this site, but on a past Google hit, I discovered that it would make Firefox go crazy. No idea why.