搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

firefox.exe process remains after closing Firefox

  • 3 个回答
  • 5 人有此问题
  • 13 次查看
  • 最后回复者为 Starwanderer

more options

I closed Firefox 5 over 45 minutes ago. At the time it closed, I had around 60 tabs open. The Firefox window closed, but now, over 30 minutes later, firefox.exe is still consuming 624 MB of memory. For the record, currently Windows Task Manager shows firefox.exe consuming 00 CPU, 639,772 K Mem Usage and a Peak Mem Usage of 771,296 K.

I'm seen this behavior at other times and, on those occasions, the firefox.exe process did eventually terminiate and release that memory. Why does firefox.exe take so long to terminate? Is this a bug or just a result of the way I use Firefox? I do tend to have a lot of tabs, 60 to 75, open at any given time. I'm guessing that's more tabs than the typical user.

I closed Firefox 5 over 45 minutes ago. At the time it closed, I had around 60 tabs open. The Firefox window closed, but now, over 30 minutes later, firefox.exe is still consuming 624 MB of memory. For the record, currently Windows Task Manager shows firefox.exe consuming 00 CPU, 639,772 K Mem Usage and a Peak Mem Usage of 771,296 K. I'm seen this behavior at other times and, on those occasions, the firefox.exe process did eventually terminiate and release that memory. Why does firefox.exe take so long to terminate? Is this a bug or just a result of the way I use Firefox? I do tend to have a lot of tabs, 60 to 75, open at any given time. I'm guessing that's more tabs than the typical user.

所有回复 (3)

more options

I should go on to add that I have already seen the Firefox Hangs |Hang at exit document and none of these look like the obvious issue. I'm running Java Version 1.6.0_26, so current there. I'm not running any of the listed Internet security software. The only extensions I'm running are Java Console 6.0.26, ReloadEvery 5.0.0 and Xmarks 4.0.1, so not a lot of extensions.

more options
more options

As I mentioned before you replied, I had already looked at that document and nothing jumped out as being the culprit. Perhaps it is a Java applet, but I am on the latest version.