4 ms·
That sounds like a bug It is a bug, but it also means that Launch doesn't consume negligible CPU. 2.6b2's default behavior is to index too agressively. There
by WalterGR 11y ago
That sounds like a bug
It is a bug, but it also means that Launch doesn't consume negligible CPU.
2.6b2's default behavior is to index too agressively. There are fixes out there, for those (like myself) who want to build their own binaries on Windows.
something to do with your system
Nope. https://www.google.com/search?q=launchy+cpu+usage https://www.google.com/search?q=launchy+cpu+usage
I'd give a better link but I'm on my phone.
- Mithaldu 11y agoOnly because other people have it as well, doesn't mean it's not an abnormality. On my system Launchy pegs a single core for 4 seconds when reindexing, and the rest of the time sits literally at 0%. I can get as much as 10% of a core out of it by holding down ctrl+space, but that's it.