Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Søg i Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Læs mere
Åben

Firefox 152.0 (64-bit) AWEFUL

Mike Caetano replied
Raven

I chose passwords and sign in, but there's more. You are already aware of the Facebook issues but there are others issues with this and I personally don't have time to tell you how to do your job. I have to keep up my production to keep my job. Your browser really cost me labor time. So, I would like to know do you recommend going back to a previous version until you fix this mess? OR... what ohter browser would you recommend as your replacement?

I appreciate your time, and I look forward to your answer.

Thank you R

I chose passwords and sign in, but there's more. You are already aware of the Facebook issues but there are others issues with this and I personally don't have time to tell you how to do your job. I have to keep up my production to keep my job. Your browser really cost me labor time. So, I would like to know do you recommend going back to a previous version until you fix this mess? OR... what ohter browser would you recommend as your replacement? I appreciate your time, and I look forward to your answer. Thank you R

Alle svar (2)

Hi,

The people who answer questions here, for the most part, are other users volunteering their time (like me), not Mozilla employees or developers.

Unfortunately, we won't be able to help you unless you share the details of the issues you experience. Also, I don't think there are known Facebook issues related to the recent update. Could you please elaborate on that?

Looking forward to your update!

Let the programmers know there is a memory leak in the main process after running update 152.0. This is a memory report taken within five minutes of opening the browser without opening any web pages, only about:processes and about:memory.

Main Process (pid 6612) Explicit Allocations

1,262.97 MB (100.0%) -- explicit ├──1,055.36 MB (83.56%) -- storage │ ├──1,041.38 MB (82.45%) -- sqlite │ │ ├──1,027.30 MB (81.34%) ── other │ │ └─────14.08 MB (01.12%) ++ (12 tiny) │ └─────13.99 MB (01.11%) ++ prefix-set ├─────54.85 MB (04.34%) -- js-non-window │ ├──36.81 MB (02.91%) -- zones │ │ ├──33.56 MB (02.66%) ++ zone(0x2125065a600) │ │ └───3.25 MB (00.26%) ++ (2 tiny) │ ├──16.45 MB (01.30%) ++ runtime │ └───1.59 MB (00.13%) ++ (3 tiny) ├─────34.67 MB (02.74%) -- script-preloader │ ├──34.67 MB (02.74%) -- heap │ │ ├──34.64 MB (02.74%) ── saved-scripts [2] │ │ └───0.03 MB (00.00%) ++ (2 tiny) │ └───0.00 MB (00.00%) ── non-heap/memmapped-cache ├─────33.40 MB (02.64%) -- window-objects │ ├──22.75 MB (01.80%) -- top(about:memory#start0, id=9)/active/window(about:memory#start0) │ │ ├──15.55 MB (01.23%) -- dom │ │ │ ├──15.52 MB (01.23%) ── orphan-nodes │ │ │ └───0.04 MB (00.00%) ++ (3 tiny) │ │ └───7.20 MB (00.57%) ++ (3 tiny) │ └──10.64 MB (00.84%) ++ (3 tiny) ├─────28.54 MB (02.26%) ── heap-unclassified ├─────24.01 MB (01.90%) ++ (27 tiny) ├─────17.96 MB (01.42%) -- startup-cache │ ├──16.76 MB (01.33%) ── data │ └───1.20 MB (00.10%) ── mapping └─────14.18 MB (01.12%) ── cert-storage/storage

Other Measurements

134,217,727.94 MB (100.0%) -- address-space ├──132,112,176.89 MB (98.43%) ── free(segments=423) ├────2,103,694.20 MB (01.57%) -- reserved │ ├──2,097,152.79 MB (01.56%) ── mapped(segments=16) │ └──────6,541.41 MB (00.00%) ── private(segments=2968) └────────1,856.84 MB (00.00%) ++ commit

208.07 MB (100.0%) -- decommitted ├──204.37 MB (98.22%) -- heap │ ├──204.03 MB (98.06%) ── decommitted │ └────0.35 MB (00.17%) ++ unused-pages ├────2.17 MB (01.04%) ── js-non-window/gc-heap/decommitted-pages └────1.53 MB (00.73%) ++ workers/workers(chrome)

2,676 (100.0%) -- event-counts └──2,676 (100.0%) -- window-objects

  ├──2,561 (95.70%) -- top(chrome://browser/content/browser.xhtml, id=1)/active
  │  ├──2,558 (95.59%) -- window(chrome://browser/content/browser.xhtml)/dom
  │  │  ├──2,544 (95.07%) ── event-listeners
  │  │  └─────14 (00.52%) ── event-targets
  │  └──────3 (00.11%) ── window(about:blank)/dom/event-targets
  ├─────53 (01.98%) -- top(chrome://extensions/content/dummy.xhtml, id=7)/active/window(chrome://extensions/content/dummy.xhtml)/dom
  │     ├──47 (01.76%) ── event-listeners
  │     └───6 (00.22%) ── event-targets
  ├─────38 (01.42%) -- top(about:memory#start0, id=9)/active/window(about:memory#start0)/dom
  │     ├──28 (01.05%) ── event-listeners
  │     └──10 (00.37%) ── event-targets
  └─────24 (00.90%) ++ top(about:processes, id=32)/active/window(about:processes)/dom
Stil et spørgsmål

Du skal logge ind på din konto for at svare på et indlæg. Start et nyt spørgsmål, hvis du ikke har en konto endnu.