搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

Firefox stops responding normally and begins 'eating' RAM.

  • 2 回覆
  • 1 有這個問題
  • 11 次檢視
  • 最近回覆由 ham2405

more options

This just started recently. When I opened walmart.com, Firefox become almost unresponsive. I discovered with Task Manager that the memory used by Firefox was continually increasing until all my RAM was used. To recover, I found that I must disconnect my RJ-45 to kill the web and get Firefox shut down. I can then replug my RJ-45 and relaunch Firefox and have no problems. If I don't unplug the RJ-45 and I relaunch Firefox, it jumps right back to the Walmart.com tab and begins eating RAM again. How do I fix this problem. BTW, there was NO change in addins or plugins when this occurred. I don't remember if there was a Firefox update about then.

This just started recently. When I opened walmart.com, Firefox become almost unresponsive. I discovered with Task Manager that the memory used by Firefox was continually increasing until all my RAM was used. To recover, I found that I must disconnect my RJ-45 to kill the web and get Firefox shut down. I can then replug my RJ-45 and relaunch Firefox and have no problems. If I don't unplug the RJ-45 and I relaunch Firefox, it jumps right back to the Walmart.com tab and begins eating RAM again. How do I fix this problem. BTW, there was NO change in addins or plugins when this occurred. I don't remember if there was a Firefox update about then.

所有回覆 (2)

more options

I had this problem with Firefox 35. Upgrading to Firefox 36 fixed the problem. Also, you should be able to end the firefox process with task manager instead of disconnecting your ethernet cable.

more options

I'm running 36. I ended firefox with task manager, but when I restarted Firefox it went right back to the walmart.com tab and eating RAM again. Disconnecting the RJ-45 and killing Firefox with task manager is the only way I could get rid of the problem. I went back to walmart.com a day or two later to see if it was an anomaly and the problem reoccurred!