Fóram Tacaíochta Firefox

After the latest update to 125.0.2 (64-bit) the browser works fine for a few minutes and then pages won't load. It starts working again after a restart [ for a few minutes]. I have cleared the cache & data. Chrome works ok.

Since the update to version 125 Firefox on Windows 11 (all updates installed), when I open a new tab and start typing to the address bar WHILE the VPN to the office is active, Firefox locks up and can not be used anymore.

In taskmanager, there is no spike in memory or cpu usage visible. All I can do at this point is to kill Firefox via taskmanager.

I can enter anything in the address bar of an already open tab with an other website open, I can open new tab from the bookmarks, but I can not open a new tab and start typing in the address bar while the VPN is active.

Once I disable the VPN to the office, everything goes back to normal.

I never had this issue on a previous version of Firefox.

Any ideas whats causing this?

FF loads so slowly and blocks so many sites that I had to disable enhanced tracking to get to mozilla.org. It can take up to 30 seconds for a site to load if I don't disable enhanced tracking, and even then, some won't load and will time out. I have 7 pinned items that load when FF opens, and it can take up to 5 minutes for all of those to load. Even on some sites where I have enhanced tracking turned off, I have to close the initial block page to get the site to load. Sometimes I have to stop the download and refresh to get the page to load. It is blocking sites that I've used for years with no problems.

What I have done: Troubleshoot mode - loaded a bit faster, but still had problems with some bookmarked pages I've used for years with no problems. It seems to hate all Google Pages, especially Google News Turned off Deceptive Content and Dangerous Software protection Turned off HTTPS only mode Turned off Block Popup Windows

I am using the apt version of firefox v125.0.2 (64-bit). I do not have a dedicated GPU - I use my intel core's internal gpu only Intel Corporation HD Graphics 620 (rev 02).

I used to play this game named narrow.one, which before I reinstalled the mentioned libraries, was working fine except for crashing a few times. I thought these libraries were causing some issue, so I tried reinstalling them.

I reinstalled the libraries using: `sudo apt install --reinstall --fix-missing libgl1* libegl*`

After installation, I start getting that error. So, I tried reinstalling firefox (using the same command), and then restarting the laptop - but of no use. Chrome seems to be running WebGL, including the game.

In firefox, on the https://get.webgl.org/ page, I see Hmm. While your browser seems to support WebGL, it is disabled or unavailable. If possible, please ensure that you are running the latest drivers for your video card.

After that, I also tried reinstalling `libopengl0` and `libglu1-mesa` and `intel-microcode`, but of no use. Running although, `sudo intel_gpu_top` and then chrome, it seems that the GPU is in use by chrome as well.

I then go to about:support. It shows me the images I have attached. Reading the logs, there several `blocklisted` values in `Decision Log` section. I suspect that's the cause of this issue, but then I don't know how can I un-blocklist the blocklisted things, and even after that, why does Chrome runs webgl if these are blocklisted?

Running `glxinfo -B`, I get the following: `name of display: :0 display: :0 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer):

   Vendor: Intel (0x8086)
   Device: Mesa Intel(R) HD Graphics 620 (KBL GT2) (0x5916)
   Version: 23.2.1
   Accelerated: yes
   Video memory: 7697MB
   Unified memory: yes
   Preferred profile: core (0x1)
   Max core profile version: 4.6
   Max compat profile version: 4.6
   Max GLES1 profile version: 1.1
   Max GLES[23] profile version: 3.2

OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) HD Graphics 620 (KBL GT2) OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.2.1-1ubuntu3.1 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.2.1-1ubuntu3.1 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.2.1-1ubuntu3.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20`

I do not know much about OpenGL, but reading the above stuff, I suppose my GPU is in use and also has a compatible driver (although I am not sure).

Also, running `glxdemo`, `glxheads`, and `glxgears` seems to be rendering stuff.

Should I reinstall firefox after purging it first? Please help.

Thanks!

I see my original question is now archived at https://support.mozilla.org/en-US/questions/1380948#question-reply I never closed it because I didn't know if my last process could really fix the issue. It didn't, not always. Over the years, there have been times when the issue would still pop up, but not as often as before (2022 and earlier).

I have a feeling that during an issue, FF is having difficulty setting up shop after starting up. Consequently, it is spending more time before it could become prepared to connect to the Net. I've come up with another "solution," which is deleting (or moving out) xulstore.json in the profile folder after exiting or before starting FF. You can create a batch command or script to execute the process.

So far, FF is connecting immediately after startup.

Canvas is working on all other browsers normally, but when I try to login on firefox an error 403 message shows up at the two factor authentification step. I allowed popups already in this browser so that is not the issue.

Hello, have been scratching my head for a while on this one. Have a freshly setup install of Debian 12, using Sway (wayland) as my Window Manager. I am really struggling with slowness in Firefox, page loads take easily 15 seconds whereas loading the exact same page in another window at the same time with Chromium Debian build has near instantaneous load times. I've tried the following troubleshooting steps: - Created a new firefox profile - Tried "Troubleshooting Mode" in Firefox - Disabled ipv6 in firefox about:config and in Debian - Tried different DNS servers - Tried different non-debian specific builds of Firefox - Tried Firefox Beta and Firefox Nightly for Debian

None of these steps made any difference, and Chromium has continued to be significantly faster. Am really stuck here and would love to get to the bottom of this as Firefox is the only browser that works with a HiDPI display in Sway without blurryness. Happy to provide any and all diagnostics and reports that are needed. Thanks in advance!

EDIT: It seems to be some kind of networking issue, using a VPN solves it. But still doesn't explain why Chromium would behave differently.

Firefox slows down when I use web developer tools, I use this whenever I try to save an image on Instagram or other sites that I go to just to save an image or look for the video using the web tools.

Is there a way to fix this issue it lags the browser or it freezes for a second.