This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

تلاش سپورٹ

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.

مزید سیکھیں

اس تھریڈ کو آرکائیوکیا گیا تھا۔ اگر آپ کو مدد کی ضرورت ہو تو براہ مہربانی نیا سوال پوچھیں۔

Firefox Quantum 61.0 (64-bit) on Windows 10 probably has a memory leak

  • 1 جواب دیں
  • 1 میں یہ مسئلہ ہے
  • 4 دیکھیں
  • آخری جواب بذریعہ SujanM

SujanM
SujanM
more options

I opened a Sacala tutorial page at http://allaboutscala.com/tutorials/chapter-3-beginner-tutorial-using-functions-scala/scala-tutorial-higher-order-function-parameter/ and just sat there for 20 minutes without doing anything else on Firefox or any other browser. I kept watching memory usage for Firefox browser in Windows Task Manager. The memory usage kept increasing from around 500 MB to over 4000 MB in 20 minutes.

I opened a Sacala tutorial page at http://allaboutscala.com/tutorials/chapter-3-beginner-tutorial-using-functions-scala/scala-tutorial-higher-order-function-parameter/ and just sat there for 20 minutes without doing anything else on Firefox or any other browser. I kept watching memory usage for Firefox browser in Windows Task Manager. The memory usage kept increasing from around 500 MB to over 4000 MB in 20 minutes.

تمام جوابات (1)

SujanM
SujanM سوال کا مالک
more options

I found the same strange behavior using Microsoft Edge browser on Windows 10 with a similar web page http://allaboutscala.com/big-data/spark/ . However, when the memory usage exceeds 4000 MB (over 95% memory utilization), the web page gets automatically refreshed and the memory usage goes down to around 300 MB. This cycle keeps repeating on Microsoft Edge. With Firefox, the page did not get automatically refreshed.