[Bug 260387] www/chromium: Aw, snap: Error code: 5
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 260387] www/chromium: Aw, snap: Error code: 5"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 16 Dec 2021 19:26:27 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260387
Jason W. Bacon <jwb@freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|Open |Closed
Resolution|--- |Works As Intended
--- Comment #6 from Jason W. Bacon <jwb@freebsd.org> ---
(In reply to sigsys from comment #5)
You ain't kidding...
I had a 16G vmem limit set on my 8G RAM laptop just to prevent low-quality
bioinformatics software from overwhelming my swap.
When I remove the limit, chromium works and this is ps shows for a single
chromium window:
UID PID PPID C PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND
2000 24760 24625 1 27 0 376072 262396 select S+ 0 0:01.04 chrome:
2000 24762 24760 1 23 0 364852 265332 select S+ 0 0:00.38 chrome:
2000 24763 24760 1 42 0 283728 226744 uwait S+ 0 0:00.15 chrome:
2000 24764 24760 0 42 0 279444 224956 uwait S+ 0 0:00.12 chrome:
2000 24765 24760 3 31 10 25481000 240272 uwait SN+ 0 0:00.32 chrome:
2000 24766 24760 1 32 10 25484460 254412 uwait SN+ 0 0:00.80 chrome:
2000 24768 24760 3 45 10 25471652 229740 uwait SN+ 0 0:00.12 chrome:
That's 3 processes using 24G virtual each + 4 more reasonable ones.
Not a fan of the "address space is free" mentality...
Thanks for the lead.
--
You are receiving this mail because:
You are the assignee for the bug.