Klaus FrankThat moment when #OpenSSH takes minutes to connect and even a "clear" takes almost 10 seconds to execute.
What the f crashed/locked-up and wtf?!?
Let's see how long it takes for htop to start and tell me...
CPU load 2.4%
Memory 494/504 GB
Swap 131/554GB
double-wtf?!?
Hmm, the tasks list also doesn't add up, there are these 192 beesd processes, but they are supposed to operate on shared memory and only have 300GB reserved right now.
And the next task (when sorted by memory) is Thunderbird with something around 1.5GB.
I know that two #KDE #Konsole windows I left open from yesterday just vanished.
Assuming they had a memory leak and they already crashed, shouldn't that memory have been freed already?
what is allocating all of this?!?
Markus Wamser@agowa338 stable advanced yesterday before nodejs and electron we're available in the binary cache, so your machine was probably choking in those builds
@wamserma It looks like it was specifically mongodb as the only package I'm pulling in from unstable is unifi and that depends on mongodb.
Everything else is using the 25.11 channel.
Except 25.11 is also affected by stable advancing?
@agowa338 with "stable" I was referring to 25.11, but likely all channels were impacted (one of the builders failed some builds due to a full disk)