WebContent process will remain after Ladybird crashed and consume CPU and Memory
I've noticed on multiple occasions that if Ladybird crashes, a WebContent process can remain and stay active, meaning it will consume significant amounts of CPU and Memory.
Example
❯ ps aux | grep -iE "ladybird|^USER"
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
ruben 1181091 24.7 1.2 1903308 205844 ? Sl 21:36 2:56 /usr/libexec/WebContent --command-line /usr/bin/Ladybird --executable-path /usr/bin/Ladybird --config-path /home/ruben/.config/Ladybird --request-server-socket 128 --image-decoder-socket 129This process remained, after visiting https://t-online.de which crashes Ladybird (#503) at the moment.
I've used Ladybird 34261e5 at the time of the crash.
LadybirdBrowser / ladybird
Truly independent web browser
21.3k
Contributors get 100% of received funds after fees
How does funding with Polar work?
1
Pay now to fund the work behind this issue.
2
Get updates on progress being made.
3
Maintainer is rewarded once the issue is completed.
FAQ
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too