Re: 1424G ... hrm?

On Tue, Apr 07, 2026 at 06:06:38PM +0200, Miroslav Lachman wrote:
> On 07/04/2026 04:27, Zaphod Beeblebrox wrote:
> > Just for example:
> > image.png
> > 
> > 
> > On Mon, Apr 6, 2026 at 10:13 PM Zaphod Beeblebrox <[email protected]
> > <mailto:[email protected]>> wrote:
> > 
> >     So... my workstation has 64G of RAM.  I've been running ungoogled-
> >     chromium and with top's thread display (H) it displays the size of
> >     the thread as 1424G.  That's 1.4T, ... I realize what virtual memory
> >     and overcommitment are ... but 1.4T of allocated space?
> 
> Nothing unusual (but still strange)
> 
>   SIZE    RES STATE    C   TIME    WCPU COMMAND
>  1380G   300M select   3   0:14   0.00% signal-desktop
>  1373G   384M uwait    0   6:03   0.91% signal-desktop
>  1366G   186M uwait    0   0:04   0.03% iridium
>  1364G   456M uwait    2   4:47   0.30% iridium
>  1364G   205M uwait    2   0:07   0.02% iridium
>  1364G   159M uwait    3   0:00   0.00% iridium
>  1364G   163M uwait    2   0:00   0.00% iridium
>    24G  2813M select   3  76:39  22.47% firefox
>    21G  2318M select   3  20:35   1.99% thunderbird
>    20G   322M select   2   0:58   0.00% librewolf
>    12G   542M select   0   4:09   0.10% firefox
>    11G  3124M kqread   2   0:05   0.00% node
>    11G   906M kqread   3   0:02   0.00% node
>  6454M   126M CPU1     1 108:52  46.08% Xorg
>  5334M   974M select   3  13:21   0.47% firefox
>  4438M   710M select   2   3:09   0.38% librewolf
>  4002M   640M select   3  11:10   1.48% firefox
> 

This is the feature of the V8 JS engine.
Google for "Sandboxed Pointers" or "Caged Pointers", AFAIR.