Firefox Support Forum

Firefox Developer 80.0b7 (64-bit) Mac Catalina V 10.15.5

I've tried using the userChrome.css file to change the background color for the active tab. create chrome folder in profile folder create userChrome.css file and add: .tab-background[selected="true"] {

 background-color: #ffffff !important;
 background-image: none !important;

} Set toolkit.legacyUserProfileCustomizations.stylesheets to TRUE Reboot mac This does not take affect and the userChrome.css file is not visible in Style Editor.

What am I doing wrong? thanks Milton

Opening links from external applications (i.e.: Outlook, Word, a PDF, etc.) begins to open a new tab in Firefox, sometimes it'll open a "full" tab-width before hanging, more often than not, I'll see a sliver of the new tab while Firefox sorts itself out.

Typically when this happens, I'll see upwards of 50% CPU usage from Firefox itself. Memory seems sane.

Hardware acceleration, whether it's on or off, makes no difference. Issue persists in safe-mode, and safe-mode with add-ons disabled. Issue persists in Firefox and Firefox Developer Edition.

Hello, I've noticed that in the very latest versions CTRL+F5 is much less efficient.

I'm using Developer Edition, 80.0b5. When I press CTRL+F5 websites very often don't reload css.

I can check this by opening the source code and opening the css file, it still shows the old version. If I press CTRL+F5 directly inside the css file, then it updates, but still the page itself won't load the updated version right away.

If I use a private window, I see all updates immediately.

Sometimes after hitting CTRL+F5 many times it will finally update.

This never happened before, is this a bug, does anybody else experience this, is there a fix?

Thanks.

After the latest update (Developer Edition 80.0b6), the developer tools console displays messages in Swedish even though I have chosen English as interface language. How do I change it back?

Hello all,

I have been experiencing a critical issue with FF for more than a year now and even though I reported it via the FF crash reporter numerous times it never got fixed so I figured I would report it here.

The issue could be summarized as follow: browsing the website mixcloud.com triggers a memory leak from FF that eventually causes my whole computer to shut down if FF cannot be "force[d] to quit" in time.

Here is a more detailed description I sent to Mixcloud support last year:

"Often times when I open a new page/tab on the website the loading freezes and after a few seconds a yellow warning notification pops up on the upper part of the screen asking: "a web page is slowing down your browser. What would like to do?” with the two following options available: "Stop it" or "Wait". If I click "stop it" the loading will indeed stop and I just have to refresh the page again to continue browsing normally. The troubles begin if I click "wait" or do nothing: the overall memory usage of Firefox will then increase seemingly exponentially and after only a few minutes the whole system will become unresponsive and I will have to hard reboot my computer or it will reboot by itself. This is extremely annoying as you can imagine as every time that happens I lose all unsaved data in the process! Strangely enough this issue sometimes even occur without any notification displayed or freeze happening in the first place: I would be browsing a few Mixcloud pages then switching to another website and after a couple of minutes I would notice that the memory usage is increasing although no Mixcloud page is open any longer... In both cases the only solution I found is to quit/force to quit Firefox as soon as possible to prevent it (and the system) to become unresponsive. Closing the application always resolves the issue and I can see the memory usage of the overall system subsequently dropping sometimes from up to 95% to 40% in the Activity Monitor app. Again I would like to stress that I have been experiencing this issue ONLY on Mixcloud and that I have no other memory related issue on my computer nor with Firefox in general."

Mixcloud support reply at the time: "this is linked to some issues we've been experiencing but our team are busy working on a fix for". 10 months later nothing changed...

The same issue happened again this very morning: I opened a Mixcloud link from google results and even though I immediately closed it, 5 minutes later the RAM usage was at 93% and I struggled during 10 minutes to "force to quit" FF as the whole computer was becoming increasingly unresponsive. I can provide a crash report from this morning but would prefer not to display it publicly.

Please investigate this leak. It is becoming more and more frustrating to deal with as the time goes by.