SUMMARY See title STEPS TO REPRODUCE 1. put https://ufile.io/i5r7q (19MB, don't know if the issue is the size or if the file is corrupted) at $HOME/.local/share/klipper/history2.lst 2. restart plasmashell (it may also hang just by waiting) OBSERVED RESULT plasmashell hangs with 100% CPU usage (might stop after a while, I only waited a couple minutes) EXPECTED RESULT system keeps working SOFTWARE/OS VERSIONS Linux/KDE Plasma: debian testing (linux 4.19.0-1-amd64) (available in About System) KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.3
Can I have your ~/.config/plasma-org.kde.plasma.desktop-appletsrc
Created attachment 117469 [details] ~/.config/plasma-org.kde.plasma.desktop-appletsrc as requested
And your ~/.config/klipperrc please
~/.config/klipperrc: [General] Version=5.8.4
Oh, I was hoping for something different. If I apply this history.lst file everything "just works". Plasma starts in a few seconds. And I have your history (some VLC playlist with music from a Game.) I'm going to struggle to do much at this point. Can you confirm if you put this history.lst back on your machine it still hangs?
>Can you confirm if you put this history.lst back on your machine it still hangs? Yes
Ok, lets see if we can find out where. can you install debug symbols for plasma-workspace from your distro. Can you get in the corrupt state and then instead of launching plasmashell run gdb --args plasmashell --replace when it's using 100% CPU and everything press control+c and type "bt" then paste that output here.
(gdb) bt #0 0x00007ffff73fbbc6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #1 0x00007ffff73fbbf8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #2 0x00007ffff73fbbf8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #3 0x00007ffff73fbbf8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #4 0x00007ffff73fbbf8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #5 0x00007ffff73fbbf8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x00007ffff73fbbf8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x00007ffff73fbbf8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x00007ffff73fbc9b in QV4::Heap::QObjectWrapper::markObjects(QV4::Heap::Base*, QV4::MarkStack*) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x00007ffff72dc83f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x00007ffff735a6b1 in QV4::PersistentValueStorage::mark(QV4::MarkStack*) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #11 0x00007ffff72dcf1b in QV4::MemoryManager::collectRoots(QV4::MarkStack*) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x00007ffff72dd143 in QV4::MemoryManager::mark() () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x00007ffff72df4da in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #14 0x00007ffff72e160d in QV4::MemoryManager::allocString(unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #15 0x00007ffff734c378 in QV4::ExecutionEngine::newString(QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #16 0x00007ffff73a5288 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #17 0x00007ffff7418b45 in QV4::Runtime::method_callProperty(QV4::ExecutionEngine*, QV4::Value*, int, QV4::Value*, int) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #18 0x00007fffd9423a51 in ?? () #19 0x00007fffe73c0340 in ?? () #20 0x00007fffe73c0350 in ?? () #21 0x00005555556382d0 in ?? () #22 0x0000000000000000 in ?? ()
Is there anything actionable here, David?
Is this still a problem for you with Plasma 5.27? Unfortunately, I cannot reproduce this since the link to the history file is no longer valid. The backtrace also has no debug symbols for anything that would help. :( If this problem is still reproducible, could you please install debug symbols, reproduce the problem, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Thanks!
changed to needsinfo
>Is this still a problem for you with Plasma 5.27? It hasn't happened for over a year AFAIR.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!