Date: Thu, 07 Jul 2022 13:45:10 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 265074] chromium pkg memory not freed after closing Message-ID: <bug-265074-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D265074 Bug ID: 265074 Summary: chromium pkg memory not freed after closing Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: hrothgar.ofstingan@gmail.com 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=20 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 t= his version fixes memory problems like use after free: https://chromereleases.googleblog.com/2022/06/stable-channel-update-for-des= ktop_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 quit= s. (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 com= pare after starting chrome and after quitting chrome, and note that the memory u= sage doesn't return back to normal). I'm unsure if any other users/systems are affected. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-265074-7788>