Komunitné fórum Firefox

Dear Firefox Support,

Since yesterday, I’ve been experiencing an issue where the entire browser randomly freezes for a few seconds. When this happens, everything stops — I can’t open or close tabs or windows, and I can’t type in the address bar. If I’m typing something when it freezes, the input seems to be stored in the background and then appears all at once after about 5 seconds, when the browser becomes responsive again. All add-ons are disabled, the computer has been restarted, and the latest version of Firefox is installed. This issue started just yesterday — before that, everything was working perfectly. No new programs were installed, and all other applications on my system are functioning normally. When I switch to Chrome, there are no issues at all. Thank you for your help.

Best regards, Peter

When typing to search, address etc keyboard inputs are not being accepted. The typing here is fine but attempting a search or entering a url or even the space bar nothing happens.

Hi, I am writing from a fresh Nobara 42 install, using Gnome 48 and the default Wayland session. Firefox version is 144.0.2. I'm not sure this is the proper channel to report a bug, I expected a more standard form. Please redirect me if you know of a better place.

Essentially : click+drag using the tablet doesn't work, be it on web content or on the GUI. When I click+drag to move a tab, the rab is ripped off into a new window as soon as the drag event begins. This happens with both regular & vertical tabs. Simply clicking tabs -without moving the pen enough to trigger a drag event- activates them normally. Click+drag on a bookmark or history item does not work either. When doing so on a bookmark folder, it seems to be always registered as a click, and it consistently triggers the opening/closing of the folder, regardless of the distance traveled by the pointer between the press event and the release event.

Exception : click+drag to select text works fine. However, click+drag to move that text into the address bar to look it up does not work. The text stays selected, the pointer icon doesn't change to indicate that something is being dragged.

Note : I am using the terms "press event", "drag event" and "release event" liberally here. I don't actually know how this all works, it's magic to me. But I felt like this was the most straightforward way of communicating what's happening.

I have a mouse to the side, that I use only for this. But it would be nice to be rid of this necessity. Any help is welcome! Thank you.

Hadrien

(My laptop is very slow. I have cleaned the cashe, performed disc cleanup, cleaned the memory, and everything i can think of. I opened task manager and see that multiple instances of Firefox open. (photo #1) I have uninstalled and reinstalled to no avail. I have also tried changing the preferences to 1 instance, but it wont allow me to. (photo #2) Please help.

I am receiving a not responding message when I try to use Firefox on my Dell Inspiron 3880 with Windows 11

I have tried uninstalling and reinstalling but get the same message.

I am using Firefox on my MacOS Tahoe. There is a persistent annoying issue where whenever I close (physically fold) my laptop screen and reopen it, Firefox will be frozen. It will be frozen in the sense that I am unable to interact with any tabs or anything until I manually quit Firefox and reopen it (which automatically reopens all my tabs), making it usable again. This doesn't happen every time I close and reopen my Mac, but it definitely happens the majority of the time and makes the browser hard to use.

I've attached a screenshot of what a new window looks like when Firefox is frozen. It looks just like a Firefox window when unfocused.

Notes:

• It doesn't entirely freeze Firefox. In fact, I can "switch" to a different tab by clicking on the tab and then shutting and reopening my laptop again. The new tab will show on reopening but Firefox will still be frozen. This process can be repeated.
• I can pretty consistently replicate the bug by shutting my laptop, waiting 10 seconds, and reopening it. This will almost always result in the freeze.
• The bug still happens if I'm not focused on the Firefox window but on a different app.
• The bug doesn't seem to happen if I just lock my screen but don't shut it closed.

Things I've tried that haven't fixed it:

• Updating my OS.
• Restarting my laptop.
• Disabling hardware acceleration.
• Disabling themes and extensions.
• Deleting and reinstalling Firefox, including deleting the user data in the "Library/Application Support" folder.

Let me know if there's any more information I can provide or fixes I can try. Also let me know if I should go ahead and file a Firefox bug report for this. Thank you.

Firefox prevents going into hibernate mode. It only appears to blank screen until mouse is moved or lid moved. This happened on 3 year old dell and now on new lenovo. I've gotten around it by going into task manager and killing firefox before hibernating. This doesn't happen on a newly opened window. I've noticed that as you use it, in the task manager, (not sure of correct term) the amounts of firefox tasks/threads? increases but does not decrease when tabs are closed. Eventually hibernate stops until I kill the firefox program. I thought this might go away with new lenovo with twice the ram, but happens at same rate. If I forget to kill firefox, I end up with a dead battery. This doesn't happen with edge or other browsers I've tried.

Ever since the last update or so (I'm currently on 145.0.2), simply opening a YouTube tab is enough to bring my browser to halt. Looking at the activity monitor on my Mac shows "FirefoxCP Isolated Web Content" using an insane amount of resources, multiple instances of 101% load on my late 2023 MacBook Pro (M3 chip).

Any ideas?

The last couple of weeks or so (as of 121025), using Firefox is very slow. Is this another Firefox update issue, or Microsoft update issue, Norton update issue or a combination of different updates that aren't working together as has happened many times over the last few years.

Any known solutions to this new problem?

Thanks

Ron