https://bugs.kde.org/show_bug.cgi?id=490952
TraceyC <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REPORTED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #23 from TraceyC <[email protected]> --- Thanks for testing with Wayland, and sorry we couldn't follow up until now. This should not have been marked CONFIRMED yet. We use that status for when a bug has been reproduced by one of the bug triagers or developers, or has enough duplicates that we have high confidence it can be reproduced by a developer. >From the addon reviews, the freezing problem doesn't occur only with Linux, it has also happened with Windows: > 5-2-23: Hard to hard reboot my laptop when this addon froze my windows system > and there was NO WAY to recover from it's supposed total capture of the > webpage. Unacceptable, do not use. I can reproduce this on Plasma built from git-master, and Firefox, using the steps in Comment 13 as well as with file:///tmp/kdeconnect.daemon-mWsnSw/1766621425735.PNG When the image is copied, I see a brief cpu spike, in top, from WebExtensions (from Firefox's addons). The system load also increases slightly and then drops off after the image is copied to the clipboard. The hang is very brief, probably because this is a newer system with good hardware. Additionally, in the flamegraph that's attached, the "jank" section shows Firefox as the parent process causing it. Part of it is the graphics image decoding, happening within the browser. >From these observations, and from prior conclusions that the hang doesn't happen with other screenshot methods such as the one built into Firefox, my strong suspicion is that the addon is simply not optimized. It's consuming system resources more than it would if it was coded better, and that likely is what caused the brief system hang. I recommend contacting the developer of the Nimbus addon so they can investigate further. There's not likely anything KDE can do unless it can be proven that KDE code is causing the issue. -- You are receiving this mail because: You are watching all bug changes.
