Chromium don't release memory when closing if sandboxed (default) and swap is used Reproducible: Always Steps to Reproduce: 1. start chromium (sandboxed by default) 2. fill the memory with any other app so the computer start swapping 3. try to quit, kill or kill -9 chromium Actual Results: Chromium stays in D status and never release the memory used. Expected Results: Chromium exit and release the memory used. Don't happend if chromium start with --no-sandbox option.
(In reply to comment #0) > Chromium don't release memory when closing if sandboxed (default) and swap is > used What version of www-client/chromium? > Actual Results: > Chromium stays in D status and never release the memory used. That's pretty bad, and may be kernel-related. What's your kernel version (uname -r)? Also, is it a renderer process, main browser process or some other process? You can determine that by looking at the browser's Task Manager and noting the PID of each process (and its type) before quitting. Please post the contents of about:sandbox in your browser.
(In reply to comment #1) > (In reply to comment #0) > > Chromium don't release memory when closing if sandboxed (default) and swap is > > used > > What version of www-client/chromium? www-client/chromium-19.0.1036.7 > > > Actual Results: > > Chromium stays in D status and never release the memory used. > > That's pretty bad, and may be kernel-related. What's your kernel version (uname > -r)? 3.2.6-gentoo > > Also, is it a renderer process, main browser process or some other process? > > You can determine that by looking at the browser's Task Manager and noting the > PID of each process (and its type) before quitting. Here is some free -h : Start of the computer : total used free shared buffers cached Mem: 3,9G 965M 2,9G 0B 97M 501M -/+ buffers/cache: 366M 3,5G Swap: 5,0G 0B 5,0G Start of chromium total used free shared buffers cached Mem: 3,9G 1,9G 1,9G 0B 103M 608M -/+ buffers/cache: 1,2G 2,6G Swap: 5,0G 0B 5,0G After quitting chromium total used free shared buffers cached Mem: 3,9G 2,8G 1,1G 0B 21M 185M -/+ buffers/cache: 2,6G 1,3G Swap: 5,0G 191M 4,8G ps aux | grep chrome alex 7735 0.0 0.0 0 0 pts/1 D 19:51 0:00 [chrome_sandbox] alex 10101 0.0 0.0 0 0 pts/1 D 19:53 0:00 [chrome_sandbox] 7735 and 10101 are not listed in the browser's Task Manager so I don't know who they are... > > Please post the contents of about:sandbox in your browser. Sandbox SUID Oui Espaces de noms PID Oui Espaces de noms réseau Oui Sandbox seccomp Non Sorry it's in french, but it seems OK
(In reply to comment #2) > (In reply to comment #1) > > (In reply to comment #0) > > > Chromium don't release memory when closing if sandboxed (default) and swap is > > > used > > > > What version of www-client/chromium? > > www-client/chromium-19.0.1036.7 > > > > > > Actual Results: > > > Chromium stays in D status and never release the memory used. > > > > That's pretty bad, and may be kernel-related. What's your kernel version (uname > > -r)? > > 3.2.6-gentoo > > > > > Also, is it a renderer process, main browser process or some other process? > > > > You can determine that by looking at the browser's Task Manager and noting the > > PID of each process (and its type) before quitting. > > Here is some free -h : > > Start of the computer : > total used free shared buffers cached > Mem: 3,9G 965M 2,9G 0B 97M 501M > -/+ buffers/cache: 366M 3,5G > Swap: 5,0G 0B 5,0G > > Start of chromium > total used free shared buffers cached > Mem: 3,9G 1,9G 1,9G 0B 103M 608M > -/+ buffers/cache: 1,2G 2,6G > Swap: 5,0G 0B 5,0G > I forgot to say that before quitting chromium, I used it while emerging some things > After quitting chromium > total used free shared buffers cached > Mem: 3,9G 2,8G 1,1G 0B 21M 185M > -/+ buffers/cache: 2,6G 1,3G > Swap: 5,0G 191M 4,8G > > ps aux | grep chrome > alex 7735 0.0 0.0 0 0 pts/1 D 19:51 0:00 > [chrome_sandbox] > alex 10101 0.0 0.0 0 0 pts/1 D 19:53 0:00 > [chrome_sandbox] > > 7735 and 10101 are not listed in the browser's Task Manager so I don't know who > they are... > > > > > Please post the contents of about:sandbox in your browser. > Sandbox SUID Oui > Espaces de noms PID Oui > Espaces de noms réseau Oui > Sandbox seccomp Non > Sorry it's in french, but it seems OK
$ cat /proc/$PID/wchan or even better $ cat /proc/$PID/stack where PID -- PID of a process in D-state.
Also attach .config just in case /boot/config-$(uname -r) or /proc/config.gz
(In reply to comment #4) > $ cat /proc/$PID/wchan 0 > > or even better > > $ cat /proc/$PID/stack I don't have this > > where PID -- PID of a process in D-state.
Created attachment 302287 [details] Kernel config
(In reply to comment #6) > (In reply to comment #4) > > $ cat /proc/$PID/wchan > > 0 hmm Do you see /proc/$PID/syscall ?
Are you able to reproduce with 19.0.1041.0? I'm not asking this blindly, it seems similar to an upstream bug claimed to be fixed (sorry I have no link to it).
(In reply to comment #9) > Are you able to reproduce with 19.0.1041.0? I'm not asking this blindly, it > seems similar to an upstream bug claimed to be fixed (sorry I have no link to > it). yes... (In reply to comment #8) > (In reply to comment #6) > > (In reply to comment #4) > > > $ cat /proc/$PID/wchan > > > > 0 > > hmm > > Do you see /proc/$PID/syscall ? yes, it contains the following : 231 0x0 0x3c 0x0 0x31139a5210 0xe7 0xffffffffffffff80 0x7fff1b2ab7d0 0x31136b1d18
231 is sys_exit_group()
(In reply to comment #11) > 231 is sys_exit_group() which means what ?
Is this possibly a duplicate of bug #413637 ? Please test with >=chromium-19.0.1084.46-r1
(In reply to comment #13) > Is this possibly a duplicate of bug #413637 ? Please test with > >=chromium-19.0.1084.46-r1 Doesn't seems to happend anymore. Thanks. *** This bug has been marked as a duplicate of bug 413637 ***