edge-frfox VS profiler

What I was trying to achieve was removing overlap highlight when highlighting the background tab. This overlay thing wasn't there on previous versions. What I want to remove when hovering over the background tab. What I want to try and achieve. If it helps, I was using this userChrome.css theme in the first place.

Firefox is my dedicated 𝓅𝑜𝓇𝓃 browser, so I use it semi-frequently as my secondary browser. The reason I won’t use it as my main browser is because it doesn’t have PWA support, it doesn’t have built-in vertical tab strip support (I don’t want to install an extension for it), and it just plain looks ugly. I installed a theme to make it look like Edge but it still doesn’t look great.

Using edge replica theme , https://github.com/bmFtZQ/edge-frfox

I've seen some similar posts about this issue already and tried all the solutions from there with no luck. After some hours I just heard my Mac fans getting crazy as usual. Hopefully this will be fixed officially since I've swapped to Firefox already. I just installed this custom theme for Firefox to make it look like Edge since I got used to Edge bookmarks look and it's been great so far.

I am switching from Firefox to brave where I use this CSS - https://github.com/bmFtZQ/edge-frfox.

If you are using Edge because you are liking it's UI. Most do. You could try this Firefox CSS : https://github.com/bmFtZQ/edge-frfox

Probably your best bet is to use the Firefox Profiler once it starts hogging the CPU to try to see what it's doing. I'd be happy to take a look at the result although I don't have a lot of experience at diagnosing performance problems; hopefully the profile will make it obvious what's going on.

I tried using the https://profiler.firefox.com/ and running with:

You can try to reproduce while taking a profile using the Firefox profiler, then share it in the #perf:mozilla.org room on Mozilla's Matrix instance.

Run a profiling session for ~30 sec when you notice something is running slower than you expect, see https://profiler.firefox.com/. Share results here if you want help interpreting them.

Next time, send a SIGABRT to the main process (kill -6 $(pidof firefox)) and use the resulting backtrace (you will find a link to the crash report in about:crashes) to file a bug. A performance profile could be useful, but you'll need to know first what to capture. This seems like a graphics issue, so try the Graphics preset. Share a link to your report.

https://profiler.firefox.com will be useful if you can capture and share it to developers.

If you can reproduce it in safe mode and a clean profile, capture a performance profile using the clean profile while trying to load a problematic webpage, don't remove any information from it, and share it here (although it's typically not easy for users to analyse them), or file a bug with it attached.

Next time, capture a performance profile using the Graphics preset, and kill the browser by entering kill -6 $(pidof firefox) in a shell. This will create a bug report (unless debian disables the crash reporter) that would indicate where Firefox is stuck at. You might need to use an official build to get useful results.