Nyxt uses about 40% of a CPU when idling

[MaxGyver83]

Nyxt uses about 40% of a CPU when idling

[aadcg]

@MaxGyver83, I started Nyxt with the file you have attached. Even though I have only one web buffer open, the CPU usage of the Nyxt process is started at about 20% and it seems to slowly decrease as time goes by (went down to 8% in ~6 minutes).

I don't think we have something meaningful or crystal clear to address here.

[jmercouris]

Do you experience the same CPU usage with the flatpak?

[aadcg]

I can't reproduce. What happens when you launch via nyxt --failsafe?

[MaxGyver83]

nyxt --failsafe uses close to 0 % CPU. Maybe because it doesn't restore any buffers? I tried to open github.com but after typing github in the "Open URL" prompt, Nyxt froze (version 3.8.0 now). The last output in the command line is:

(process:2): GLib-GIO-WARNING **: 23:06:56.088: Socket check failed

** (process:2): WARNING **: 23:06:56.354: Error writing credentials to socket: Fehler beim Senden der Nachricht: Datenübergabe unterbrochen (broken pipe)

(I'll try to reproduce this with an English output.)

[MaxGyver83]

Do you experience the same CPU usage with the flatpak?

I'm going to install flatpak and try again (today or tomorrow).

Update: I need to clean up my partition first. It's almost full. So I won't test this today anymore.

[aadcg]

nyxt --failsafe uses close to 0 % CPU. Maybe because it doesn't restore any buffers?

What happens when you launch as nyxt --no-config --no-auto-config?

[MaxGyver83]

What happens when you launch as nyxt --no-config --no-auto-config?

Again around 40 % CPU usage.

[aadcg]

Again around 40 % CPU usage.

This seems to suggest that it is related to loading either /home/max/.local/share/nyxt/history/default.lisp or /home/max/.local/share/nyxt/auto-rules.lisp. Can you backup these files (by copying them to another location) and start Nyxt by keeping one of those and then the other?

[MaxGyver83]

But now I have closed 10 to 15 buffers. Now the CPU usage is close to 0% when Nyxt is in the background, and 10 to 30 % when I focus it and do something like switching to another buffer.

[aadcg]

If it is related to the number of open buffers, then you can try to start Nyxt via nyxt --failsafe and then open 15 buffers and check the CPU usage.

Then the question is whether other browsers based on WebKitGTK suffer from the same fate. Notice that we're working on #2989.

[MaxGyver83]

OK, after opening some buffers, it still looks good. I'll try again with more buffers and compare with other browsers.

[jmercouris]

Sometimes specific websites can use a TON of CPU, not sure why that is. I guess they are running some crazy javascript loop. Would be interesting if we could see the CPU usage for each buffer to allow the user to kill the resource heavy buffers in the kill-buffer prompt.

[MaxGyver83]

Today, I was back at 40 % CPU usage. Then I restarted Nyxt, and the CPU usage was only at 20 - 30%. Next, I tried again with the failsafe flag. But when I start without any buffers, CPU usage is minimal. I tried using --failsafe but still loading the buffers I had open before:

./nyxt --failsafe --load ~/.local/share/nyxt/history/default.lisp

But this seems not to be the right way. I ended up with only one empty buffer.

In case you want to try to reproduce with my buffer list, here it is:
default.txt
(Rename to default.lisp.)