I-Firefox Community Forum

I know this probably sounds odd but I'm not imagining it. I like many people I live with many tabs open at once. Since the 143 update I come back to my computer the next morning and many of my tabs, specifically my gmail tab and many others will not work. (Oddly I've noticed some random tabs will still work, I have no idea why) I can close the tab and try to reopen gmail in a new tab and it just sits there trying to open but it will not. I've waited 20 minutes. Not until I close firefox and restore my last session will it again work properly. Is there a bug/glitch or is there some setting I need to adjust. I don't want to have to close my firefox everyday. Edge is not having this same issue, so I'm pretty sure it's not a problem with my specific machine. It's like Firefox just decides to quit when I go to bed. I know it sounds crazy.

I'm running the latest version of Windows 10 and Firefox 143.0.1.

I recently bought my first OLED monitor, so I enabled auto-hide taskbar in Windows to try and reduce the chance of burn-in. However, while it works for the most part, it seems to often break in Firefox where the taskbar will hide, but not reappear when I move my mouse pointer to the bottom of the screen.

You can replicate this issue by having FF not maximised, then dragging its window titlebar to the top of the screen and letting go in order to maximise it. At that point, the taskbar no longer pops up when you mouse over the bottom of the screen.

Many thanks for any help you can give.

I have tried safe mode. No joy, but it has shown plain vanilla FF is the issue, not extensions.

(I'm using a different browser to make this report, so Share Data button is of no use here.)

Description: We have encountered a significant performance issue with NativeMessaging API in Firefox when an extension communicates with a native application.

In scenarios where many objects must be enumerated (e.g., ~458 certificates), Firefox is dozens of times slower than Chromium-based browsers.

Environment:

Firefox (latest stable, reproduced in 2025)

Windows 11 x64

Same machine and same native plugin tested in Chrome, Edge, Yandex Browser

Steps to Reproduce:

Create a WebExtension that communicates with a native application via NativeMessaging.

Perform enumeration of a large number of objects (≈ 450–500).

Measure execution time in Firefox vs Chromium.

Actual results:

Firefox: enumeration of 458 objects takes ~2 min 30 sec

Chromium/Edge/Yandex Browser: enumeration of the same 458 objects takes ~5 sec

Additional tests: Round-trip time (RTT) for a single message:

Firefox: ~73.7 ms

Chromium: ~0.3 ms

Because the extension and the plugin exchange a large number of messages, this performance gap becomes critical.

Expected results: NativeMessaging API in Firefox should perform at a level comparable to Chromium browsers, so that extensions relying on heavy message exchange remain usable.

References: Bug 1288912 – Native messaging performance is extremely poor

Although this bug is marked as resolved, performance testing still shows a major discrepancy in the current versions of Firefox.

Question: Is there any ongoing work or plan to optimize the implementation of NativeMessaging API in Firefox to address this performance issue?

Windows 10 Open Firefox (151.0.2) Google "does alton towers still run in the rain"

My CPU then goes to 100% continuously. Why, CPU occupancy has only gone up in the last few weeks. This happens in a lot of searches.

Hi, I’ve been experiencing slow startup times in Firefox, especially when I have my Time calculator web app open. The browser takes longer to load and sometimes becomes unresponsive.

I’ve tried disabling extensions and changing my home page, but the issue persists. Are there any specific settings or troubleshooting steps in Firefox that can help improve performance when using online calculators like this?

Any guidance or tips would be greatly appreciated. Thanks!

Ever since this month's Windows 10 update I've been having problems with Firefox. I start it, the menu bar and tab comes up, but then nothing. I can't access any web sites. I tried removing the Windows update, then tried uninstalling and reinstalling Firefox, and then messing with the settings. In each case Firefox would work for a couple of days, then I'd have to start it three or four times to get it to work, then it wouldn't work at all. I've been using it for 10 or more years now (four on this computer) and have never had any problems before. I'm loathe to switch to another browser, but if this can't be fixed I won't have any choice. This is what happens when I start the program.

Hello Firefox Support,

Since the latest update of the Firefox browser, I have been experiencing frequent freezes. The browser becomes unresponsive when performing basic actions such as:

• Clicking on the menu

• Closing tabs

• Copying or editing the URL

When this happens, the only way to recover is to close Firefox and reopen it.

Could you please advise on how to resolve this issue?

Thank you for your support.

Best regards, Mohamed Adel

Hello,

I have several PC;s but all suffer on occasion absurdly slow performance when a Firefox update is released.

I may be wrong but it appears there are too many of these processes running, I tried changing the value in " about:config " but Firefox defaults the value back to " 12 " when the browser is restarted.

" app.normandy.migrationsApplied 12 "

The below details are from a small, new cube pc that runs great, it is slow but does perform well, even previously just the other day running multiple Live Youtube streams with no issues, until now. :)

Any help would be great. Thank you!!!

" Firefox 142.0.1 (64-bit) "

Device Name Garage Processor Intel(R) Celeron(R) N4020 CPU @ 1.10GHz 1.10 GHz Installed RAM 4.00 GB (3.83 GB usable) Storage 58 GB SSD VID:32 MMC64G Graphics Card Intel(R) UHD Graphics 600 (128 MB) Device ID C12EB49A-0C22-41C3-A8E6-4420E4A419B0 Product ID 00330-50441-82637-AAOEM System Type 64-bit operating system, x64-based processor Pen and touch No pen or touch input is available for this display