https://bugs.kde.org/show_bug.cgi?id=430173
--- Comment #2 from ircha...@airmail.cc --- as I said in the comment I'm using it with the b and n flags as I run mine in the background normally, and having a notification show has the process running until the notification is gone. Having both flags ensures that the process ends as soon as the screenshot is taken. Whether I run it from a keyboard shortcut or from terminal the result is the same: degraded performance from the second consecutive screenshot. To measure the impact I did it with two programs, with the simple time and with hyperfine. Just running "time spectacle -bn" consecutively shows the degradation which is: 1. running "time spectacle -bn" the first time 2. as soon as the process finishes run it a second time 3. see how that point onward it takes a lot more time to finish execution waiting for a little while, like say, 10 seconds, will make the next execution be fast again. The other, more controlled method, is using hyperfine https://github.com/sharkdp/hyperfine and just doing the following command: 1. hyperfine 'spectacle -bn' from which my results are: Time (mean ± σ): 4.915 s ± 1.491 s [User: 417.8 ms, System: 67.4 ms] Range (min … max): 0.673 s … 5.443 s 10 runs -- You are receiving this mail because: You are watching all bug changes.
