0 Members and 1 Guest are viewing this topic.
Why does it sometimes take forever to close a [firefox] window?
When Firefox makes an NPAPI call to a plugin which is running in its own process, the NPAPI call is translated into an inter-process communication (IPC) request that is posted to the process. Firefox then waits for the response. If a response is not received within a given amount of time (by default, this is 45 seconds), the plugin is assumed to have locked up, and Firefox terminates the plugin ...
... Currently my version is using 1.1G of memory ...
... Still the biggest CPU user at 23% currently
Every once in a while, I find Firefox is using far too much memory, perhaps due to my bad habit of opening multiple windows, and using lots of tabs. Should one use the "normal" shutdown? Or just use the task manager and kill the process?
Why does it sometimes take forever to close a window?
Do websites have a "phone-home" portion? WHY?
I realize that applications such as Wordprocessors or Spreadsheets will have a "saved file" check on closing. But, for most other applications, I would just like it to quit immediately when closing. The memory manager should be able to deal with memory. Is the problem dealing with temporary files? Is there a better way to deal with temporary files, perhaps using a garbage collection routine like memory?