Firefox Community Forum

Firefox dropdowns, menus and popup menus do not appear after resume from suspend on Ubuntu 22 or 24 This has been happening for only the last few weeks. Even dropdowns on web pages do not appear. I can click the dropdown and cursor down then hit ENTER to change a dropdown's value but I cannot see anything while I'm doing it. On the menus, I can use hotkeys if I remember them but the menus themselves do not appear. Right-clicking to get a context menu also does nothing but it behaves like it did. If I right click something, nothing changes on screen but if I then click another link or button, the first click is swallowed to dismiss the non-existent popup.

Other apps on the system work fine including Chromium browser.

This only occurs if I start Firefox then suspend the machine and then resume from suspend. After resume, the menus, dropdowns and popups no longer appear.

I am running Ubuntu 24.04.4 LTS on a Dell Optiplex 3050, Core i3-7100x4 , 16 GB ram, Intel HD graphics 630 (KBL GT2), Gnome 46, Wayland windowing system.

I tried Firefox safe mode, clearing the caches, etc. Nothing worked.

I am on a new PC with Windows 11, using 4 monitors. I keep trying to figure out what is making my mouse and sometimes the keyboard behave sluggish (freezes for a moment). I have takes all suggestions that AI has suggested but it is still happening. Do you have any thing for me to try? It appears to be only when Firefox is running.

• • Background:**

I'm a senior software engineer running Firefox Developer Edition on a Linux machine with 8GB RAM. I have Fission architecture (site isolation) enabled, which I understand is now the default since Firefox 95+.

• • The problem:**

When I open 20 or more tabs across different domains, Firefox's memory consumption scales dramatically — often reaching 4–6GB of RAM for what should be lightweight browsing sessions. This is significantly higher than what I observed before Fission was enabled.

• • What I've already tried:**

- Disabled hardware acceleration → no significant improvement - Set browser.tabs.unloadOnLowMemory to true → partial relief

 but tabs reload constantly, disrupting workflow

- Reduced content.notify.interval → marginal improvement - Tested with all extensions disabled (safe mode) → RAM usage

 still high, confirming it's not extension-related

- Checked about:memory → large number of separate

 "Web Content" processes, one per origin as expected with Fission

• • What I'm trying to understand:**

1. Is there a way to set a maximum process count cap for Fission

  without fully disabling site isolation? I found 
  dom.ipc.processCount but changing it doesn't seem to affect 
  Fission's per-origin process spawning behavior.

2. Is browser.tabs.min-warm-process-count a relevant setting here

  and what is the safe range to modify it?

3. Does Firefox have a built-in memory pressure threshold where

  it automatically consolidates processes — similar to Chrome's 
  memory saver — and if so, which about:config keys control it?

• • Environment:**

- Firefox Developer Edition 151.0b10 - OS: Ubuntu 24.04 LTS - RAM: 8GB - Fission enabled: confirmed via about:support - Extensions: disabled for testing

My Firefox 150.0.3 (64-bit) in Windows 11 on a Dell 9310 locks up when the XPS is put sleep and awakened after 5-minutes or so. No recent Extensions or Add-ons have been installed. I have yet to delete and reinstall Firefox, maybe that's the next stop. I just can't find the problem with my limited tools and experience. Thanks, and appreciate the help.