Earlier today I went to save a file in Firefox, using the keyboard to switch to the desired folder, when the explorer save box almost became totally unresponsive (The help button, near the close button would change the cursor, but clicking any other control in the dialog didn't produce the usual behaviour).
I then realised that my Firefox windows, with probably ~100 tabs (Only 10-20 loaded), had stopped responding also. The process has been consuming the above resources and no script timeout warning has been displayed in the last several hours of me researching ways to deal with this.
This isn't the first time something similar to this has happened, as I usually leave tabs up until the info in them is no longer useful, which leads to many being loaded at any one time, and more still that are in the tabs list, but left unloaded.
I presume that the symptoms indicate a process is stuck in a endless loop, or is stuck not being able to swap out memory to complete an operation, no?
What I am mainly wondering is - Is there a way of closing a tab, or something, while Firefox is in this state, to resume some resemblance of normal operation. Perhaps some sort of memory manipulation technique / tool, so in future instances I don't have to start a large non-resumable downloaded again, or this time save some information in a form Lazarus isn't likely to have saved?
Also, I once read about a limitation of the XUL platform, that was related to maximum RAM size of a instance (or similar), but cannot find any info through google about this now. Would be great if someone could point me to this information again.
