Using FreeBSD 13.1-RELEASE on amd64 installed chrome via pkg, not port, since the pkg version claims to be more up-to-date release Version 103.0.5060.53 (Official Build) (64-bit) vs. 100.0.4896.60 (as listed in /usr/ports/www/chromium/Makefile ) (I haven't bothered to test the ports version for obvious reasons) Strangely, I read about a perhaps related bug today seems to suggest that this version fixes memory problems like use after free: https://chromereleases.googleblog.com/2022/06/stable-channel-update-for-desktop_21.html But, on my old mac mini 4GB ram edition on FreeBSD, I see memory usage at around 3.5 gigs free after startxing into twm, but after starting chrome and quitting, that drops down to about 2.8 gigs and doesn't switch below that number. So, it doesn't appear to be freeing memory properly when the programme quits. (Obviously, this is simple to reproduce, reboot a FreeBSD system; startx or xinit to get a minimal environment, run top (to see memory usage), then compare after starting chrome and after quitting chrome, and note that the memory usage doesn't return back to normal). I'm unsure if any other users/systems are affected.
@Reporter Could you provide additional information please: - Full uname -a output - pkg version -v output (as an attachment) - pkg info chromium output (as an attachment)
Created attachment 235131 [details] pkg v output as requested
Created attachment 235132 [details] pkg v output
Created attachment 235133 [details] pkg info chromium as requested
uname -a output gives: FreeBSD minim 13.1-RELEASE FreeBSD 13.1-RELEASE releng/13.1-n250148-fc952ac2212 GENERIC amd64
Created attachment 235134 [details] uname since I can't add due to bug file lock on bugszilla
Just as additional feedback, it's strange how the wired memory usage seems to account for the memory not being freed. Despite chrome no longer showing up under top or ps when the process is quit, it does exhibit behaviour like the memory is still reserved for the programme. (Since, restarting the programme from the shell and I get instantanenous reloading of the programme, whereas, starting from a cold restart I wait maybe 1 to 2 seconds before twm prompts me in the UI for where to place the window). Checking online, this appears to be related to the different way(s) that freebsd can manage memory. Let me know if I need to send across any more info.
(In reply to hrothgar.ofstingan from comment #0) > … doesn't appear to be freeing memory properly when the programme quits. … Via <https://bokut.in/freebsd-patch-level-table/#releng/13.1> for FreeBSD 13.1-RELEASE-p3: <https://www.freebsd.org/security/advisories/FreeBSD-EN-22:23.vm.asc> > Memory pages become unreclaimable Please review this bug with the most recently packaged Chromium on FreeBSD 13.1-RELEASE-p4.
Hi, Sorry for just seeing your update now; but my system is now 13.1-RELEASE-p5 and my chromium version is: Version 108.0.5359.98 (Official Build) (64-bit) yet the problem still persists. As I described it initially, one can actually see that the memory is still reserved for the process that locked it in the first place, since if I go to launch chromium after closing it, a check on top shows the memory usage is higher than it would have been if I had never launched chrome upon starting X, and if I restart chromium after closing it (theoretically killing all its processes) when I launch chromium again it's a helluva lot faster to load chrome. (So, the first time my old mac mini might take 1 to 2 seconds before presenting a ghost of a twm window for me to place, yet, if I close and restart I get that pretty instantaneously). So, for me, the bug is still present.