lapce pegs CPU at 100% after starting up

[zhaojiangbin]

1. Start top (or activity monitor in macOS)
2. Build this commit dd7d3b0
3. Start lapce and wait for a few seconds
4. See lapce taking the top spot with CPU at 100%

[zhaojiangbin]

Tested the debug build on macOS, intel CPU.

[bugadani]

The debug build generates extremely inefficient code, so this isn't that surprising. Unless you experience this with release mode code, I wouldn't consider this an issue.

[bugadani]

Also, you can use the fastdev profile if you need to have better performance in debug. cargo build --profile fastdev

[zhaojiangbin]

The debug build generates extremely inefficient code, so this isn't that surprising. Unless you experience this with release mode code, I wouldn't consider this an issue.

Sorry I wasn't clear. It was not CPU spikes.

When it was supposed to be idle (i.e. I wasn't doing anything with lapce after it started up), the process was keeping the CPUs at 100% according to top and activity monitor until I quit the program. The cooling fans of my laptop were running loudly because of this.

The previous commits do not have this problem.

[ttytm]

Same problem with cpu usage going crazy on linux.

Even using a 16 core 4,5ghz each cpu it gets really loud.

[dzhou121]

Can you please test the latest master? Previously Lapce scans all the font files at startup which now changed to be lazy loading.

[zhaojiangbin]

Can you please test the latest master? Previously Lapce scans all the font files at startup which now changed to be lazy loading.

Yep it is now fixed for me.

[ttytm]

Look good to me too!

[bugadani]

Thanks for the feedback. I assume this issue is fixed now, but please feel free to reopen if you experience it again!