[3285725978] Upstream Reporter: SSkeries
Upstream issue status: Closed
Upstream description:

https://issues.redhat.com/browse/COCKPIT-1332

Explain what happens

As of now i haven't been able to identify how exactly it happens, but i have been experiencing this pretty much since setting up the system.

At some point, either when already connected and switching between menu items or merely logging in the web interface will slow to a crawl, usually indicating that this specific issue has manifested.
At this point one CPU core is pinned to 100% usage by cockpit-tls. If i then retry switching or refresh the browser, additional CPU cores shoot up to 100% until the system runs out of cores and becomes entirely unresponsive.
At this point i have up until now resided to log in via SSH and kill the process, but of course that's merely a workaround.

This is a fresh install of Fedora 42 Server, using podman rootless containers on an Intel N150 SoC with 16GB of RAM and a Samsung 980 500G. Installed cockpit extensions are Files, Machines, Networking, Podman, SELinux and Storage; installed via cockpit.

I'll gladly provide logs, trace things and do config changes. Just point me in the right direction.

Version of Cockpit

343

Where is the problem in Cockpit?

Navigation & Shell

Server operating system

Fedora

Server operating system version

Fedora Server 42

What browsers are you using?

Firefox, Safari on iPhone

System log