This machine was continuously upgraded since precise. The problem only occurred in raring, I did not see this behavior with older kernels.
It also has not recurred with the v3.9-rc2-raring kernel.
> I wonder if Firefox could have a memory leak, if this only
> happens when Firefox is running?
Firefox may or may not have a memory leak, but the issue here is the way in which the kernel is managing swap in a situation where there should still be far more than enough memory for everything. Reserving 1.2GB of system memory for page caches and going into a swap death when hitting that limit is not reasonable behavior for the kernel.
Do you want to step me through a kernel bisect, so we can try to find the commit that fixes it between 3.8.0 and 3.9-rc2?
This machine was continuously upgraded since precise. The problem only occurred in raring, I did not see this behavior with older kernels.
It also has not recurred with the v3.9-rc2-raring kernel.
> I wonder if Firefox could have a memory leak, if this only
> happens when Firefox is running?
Firefox may or may not have a memory leak, but the issue here is the way in which the kernel is managing swap in a situation where there should still be far more than enough memory for everything. Reserving 1.2GB of system memory for page caches and going into a swap death when hitting that limit is not reasonable behavior for the kernel.
Do you want to step me through a kernel bisect, so we can try to find the commit that fixes it between 3.8.0 and 3.9-rc2?