[plasmashell] [Bug 405667] Plasmashell And Google Chrome Freeze

2019-04-03 Thread naroyce
https://bugs.kde.org/show_bug.cgi?id=405667 --- Comment #5 from naroyce --- Because the pixmaps had climbed to 200MB in less than 1 day, I thought I'd try something else... "Configure Task Manager" "Show tooltips": Uncheck "Highlight windows": Uncheck "Show progress bar and status information

[plasmashell] [Bug 405667] Plasmashell And Google Chrome Freeze

2019-04-01 Thread naroyce
https://bugs.kde.org/show_bug.cgi?id=405667 --- Comment #4 from naroyce --- In the amount of time since my last comment, I've opened the android emulator, and vlc. Nothing notable regarding pixmaps came from the emulator and vlc wasn't bad either, but the pixmaps jumped when I hovered over the

[plasmashell] [Bug 405667] Plasmashell And Google Chrome Freeze

2019-04-01 Thread naroyce
https://bugs.kde.org/show_bug.cgi?id=405667 --- Comment #3 from naroyce --- valgrind plasmashell --replace didn't do anything. kquitapp5 plasmashell timed out with "Quitting application plasmashell failed. Error reported was:\n\n org.freedesktop.DBus.Error.NoReply : Did not receive a

[plasmashell] [Bug 405667] Plasmashell And Google Chrome Freeze

2019-04-01 Thread naroyce
https://bugs.kde.org/show_bug.cgi?id=405667 --- Comment #2 from naroyce --- So chrome plays no role in the freezing based on the current freeze. Plasmashell is still frozen and I'm currently still in chrome. I SHIFT-ESC to open System Monitor and added the X11 Memory column after seeing a

[plasmashell] [Bug 405667] Plasmashell And Google Chrome Freeze

2019-03-20 Thread naroyce
https://bugs.kde.org/show_bug.cgi?id=405667 --- Comment #1 from naroyce --- Actually, the attachment is ONLY of the previous version of plasmashell, NOT chrome. >From what I could tell, trying to debug chrome is problematic. If it's needed, so too will be guidance for doing so. -- You are