Comment 6 for bug 1504914

Hi Christopher,
I've done further tests.
Regarding your question, effectively after reproducing the problem with the previous kernel I've got a crash file from google-chrome. Even with the default values mentioned in #3
What I've observed is:
- when having swap off the problem arrives faster when reaching the memory limit, the system just restart at logon screen (but it doesn't seem a complete reset because I didn't get the GRUB screen (more like the lightdm process restart?)
- when having swap on the problem arrives when consuming almost all the swap memory, but same issue: mouse and keyboard start not to respond and then finally restart.
- with the new kernel 3.14 the restart does not arrive but the system become equally freeze near the limit of memory and eventually require a hard reset or have to wait to be able to kill some of the process (that could take too long). But in this case google-chrome started to give unresponsive windows messages and kill their own processes himself, giving proper errors.

The steps I use to reproduce the problem are:
- execute $ sudo memtester 2G
- open almost 30 bookmarks of web pages as tabs of google-chrome
- eventually execute $ sudo memtester 1G (when using swap to reach the limit again)