Форум поддержки Firefox

Need help figuring out why Firefox has a memory leak after an extended use of Firefox browsing. Don't know if its the result of an extension having this issue, or if its a Firefox bug. I have also provided my troubleshooting information, and a link to my memory usage is listed below for download: https://1drv.ms/u/s!ArspaZQCMwZ-iLU_CckOfLkl9DlETQ?e=MuIqsO Thanks in advance!

OS version : Windows 10 Pro 21H2 Browser version : Firefox Developer Edition 126.0 Beta 8 (20240501022718) Platform : windows, Web

EVERYTHING especially

 * The time to receive the first HTTP response when connecting
 * the time to call up the various css elements that make up the screen
 * the time to call up the img elements on the screen
is too slow.

tooooooooo slow. I waited 36.6s until http response for every new URL open! Of course, I am using a lot of Firefox extensions, but there were no serious problems outside of YouTube, and the same problem occurred after removing the extension, and i also confirmed that the problem caused by web extensions on waterfall(on firefox profiler) was minor.

I can't even guess the cause of the problem, so unfortunately there seems to be no additional information that I can give you. I'll keep following up as long as I can. I will attach some pictures that might help you solve the problem. and you can also approach to my full-recorded firefox profiler data

To check my icloud email, I log into icloud.com, enter my password, got through a two step authorization process and ask to stay signed in. I successfully access my email messages. When opening a message that has a hyperlink, I lose the iclolud connection. The link opens in a new browser window, but when i return to the email I am frequently signed out. Apple support does not know what the issue is; they suggested a different browser. This does not seem to happen with Microsoft Edge - and I don't want to use it.

Thanks for your help David Bartold; dwb0224@icloud.com

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.

I've been having problems with some websites not displaying content, others displaying error messages. So have been going through the Troubleshooting Mode and diagnostic process.

The cause is the MS CoPilot extension for Firefox.

Useful in other ways as I discovered several other extensions I don't need, hence have remained disabled.