my machine has some 6 GB of RAM (discount some reserved areas and a maybe bit for the video).
recently i ran a virtual machine with some 2 GB of assigned VM memory.
clearly it loaded the system a lot making the interaction with the main OS (Win7 64bit) pretty clumsy due to permanent swapping.
rather short after closing the VM it turned out that waterfox did dramatically grow up with its memory consumption.
this lasted a quite noticeable while (the machine went pretty unusable at that time) until all calmed down again after some >5 minutes.
waterfox memory consumption during the phase was up to 4 GB whilst afterwards it only showed 1,2 GB. (i have open a bunch of tabs)
maybe its not a waterfox specific problem as it might happen in firefox as well - just waterfox can use up much more memory in such a case - thus its behaving "worse".
i have no idea what has happened - might have been some delayed operations, some plugin or some sort of garbage or cache cleanup.
the major problem is that it is using so much space making interaction with the machine & the browser drop down to a barely useable state.
if i had less memory in the machine then swapping would probably increase much and the duration of the incident would probably increase to >30 min(?).
Does someone know what that can be or how i am able to determine the root cause operation of that behaviour? (I think i had that happen a few times in the past so i probably will have it happen a few more times in future.)
memory behaviour as taken with Sysinternals process explorer at two different times of progress.
PS: after restarting the browser the memory footprint dropped down to even only 950 MB.Edited by alexstohrh - 6/30/14 at 2:57am