Date: Thu, 15 Dec 2022 15:39:24 +0000 From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 265074] www/chromium pkg memory not freed after closing Message-ID: <bug-265074-28929-pyFAeBPZuw@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-265074-28929@https.bugs.freebsd.org/bugzilla/> References: <bug-265074-28929@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D265074 --- Comment #9 from hrothgar.ofstingan@gmail.com --- 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 res= tart I get that pretty instantaneously). So, for me, the bug is still present. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-265074-28929-pyFAeBPZuw>