and guess which process was trying to claim some more memory?
hmmmm, my drive isn't full at all (tonnes of free space on top of a spacious heap of physical ram) but my HD is known to have bad sectors (waiting till school is done to replace it) so it may be VM.. though I'm barely paging in or out from the HD...
Yup, because the next thing that probably happened was some app crashed because it couldn't get VM, which then prompted the Window Manager to toss up a window explaining why the app crashed, but the WM needed RAM for the window, and... oops.
Comments
hmmmm, my drive isn't full at all (tonnes of free space on top of a spacious heap of physical ram) but my HD is known to have bad sectors (waiting till school is done to replace it) so it may be VM.. though I'm barely paging in or out from the HD...