UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.100 Safari/537.36

Steps to reproduce the problem:
1. Open several chrome apps or tabs, like: Inbox and Hangout
2. Lock the session. Wait until monitors go to sleep.
3. Leave the desktop for a couple of days
4. Login.

What is the expected behavior?
Chrome should use the same memory before locking the session.

What went wrong?
Chrome uses up all memory in system. However, after logging in, htop shows chrome is freeing up memory gradually.

However, since it has used massive amount of memory, it eventually gets killed by rlimits. dmesg shows:

[ 9713.920276] mmap: chrome (27624): VmData 2208776192 exceed data ulimit 2147483647. Update limits or use boot option ignore_rlimit_data.
[106742.664935] perf: interrupt took too long (2518 > 2500), lowering kernel.perf_event_max_sample_rate to 79000
[228970.405113] perf: interrupt took too long (3149 > 3147), lowering kernel.perf_event_max_sample_rate to 63000
[330702.324840] traps: chrome[15561] trap invalid opcode ip:557e7dd68c77 sp:7ffe68ac67d0 error:0 in chrome[557e7a11e000+6430000]
[330730.524950] traps: chrome[15562] trap invalid opcode ip:557e7dd68c77 sp:7ffe68ac67d0 error:0 in chrome[557e7a11e000+6430000]
[330771.328458] traps: chrome[15563] trap invalid opcode ip:557e7dd68c77 sp:7ffe68ac67d0 error:0 in chrome[557e7a11e000+6430000]
[330793.413935] traps: chrome[15564] trap invalid opcode ip:557e7dd68c77 sp:7ffe68ac67d0 error:0 in chrome[557e7a11e000+6430000]
[330793.801794] traps: Chrome_ProcessL[27091] trap invalid opcode ip:55bf57e92a0b sp:7ff505363c00 error:0 in chrome[55bf56e9f000+6430000]

Did this work before? N/A 

Chrome version: 54.0.2840.100  Channel: stable
OS Version: 54.0.2840.100
Flash Version: Shockwave Flash 23.0 r0

Is it possible to suspend all chrome process after locking the session?