Comment 4 for bug 1359766

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I was unable to reproduce this issue on my machine, which has an SSD drive.

I'm using the eatmemory program found at:
https://github.com/julman99/eatmemory

I run eatmemory and pass it an argument of 10G. I can see the program start to consume memory by using vmstat and top. However, an oomkill happened right when all them memory was exhausted and the eatmemory process was killed.

I didn't notice any effect on interactive performance once the OOM kill happened.