Summary: | Plasmashell /usr/bin/plasmashell increases CPU usage until crash | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | brian |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | bhush94, justin.zobel, kde, kolAflash, plasma-bugs |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.4.1 | ||
Target Milestone: | 1.0 | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
brian
2015-09-16 20:26:43 UTC
I have done the following in attempts to resolve this bug. Tried updating processor microcode https://wiki.archlinux.org/index.php/Microcode#Installation Tried fixing a reported intel problem causing crashing with this workaround http://goo.gl/DlLJrK Obviously as seen above I've posted a Dr. Kronqi of the crash and installing debugging symbols. I have tried Nouveau and Nvidia Proprietary Drivers. I use the .340xx supported drivers. I have cleared configurations of Xorg and Plasma. To no improvement. One thing to notice is that I did a minimal installation of plasma with just pacmanning plasma-desktop instead of the whole plasma package. I then only experienced crashing of krunner not the whole plasmashell. Figured out how to run plasmashell with GDB. I've got the following from a crash: org.kde.plasma.pulseaudio: returning roles QHash((262, "Volume")(261, "Properties")(260, "Index")(267, "Description")(266, "Name")(265, "VolumeWritable")(264, "HasVolume")(270, "ActivePortIndex")(269, "Ports")(268, "CardIndex")(259, "ObjectName")(258, "PulseObject")(257, "Index")(263, "Muted")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 261 "Properties" org.kde.plasma.pulseaudio: returning roles QHash((262, "Volume")(261, "Properties")(260, "Index")(267, "Description")(266, "Name")(265, "VolumeWritable")(264, "HasVolume")(270, "ActivePortIndex")(269, "Ports")(268, "CardIndex")(259, "ObjectName")(258, "PulseObject")(257, "Index")(263, "Muted")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 262 "Volume" org.kde.plasma.pulseaudio: returning roles QHash((262, "Volume")(261, "Properties")(260, "Index")(267, "Description")(266, "Name")(265, "VolumeWritable")(264, "HasVolume")(270, "ActivePortIndex")(269, "Ports")(268, "CardIndex")(259, "ObjectName")(258, "PulseObject")(257, "Index")(263, "Muted")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 268 "CardIndex" org.kde.plasma.pulseaudio: returning roles QHash((262, "Volume")(261, "Properties")(260, "Index")(267, "Description")(266, "Name")(265, "VolumeWritable")(264, "HasVolume")(270, "ActivePortIndex")(269, "Ports")(268, "CardIndex")(259, "ObjectName")(258, "PulseObject")(257, "Index")(263, "Muted")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 269 "Ports" org.kde.plasma.pulseaudio: returning roles QHash((262, "Volume")(261, "Properties")(260, "Index")(267, "Description")(266, "Name")(265, "VolumeWritable")(264, "HasVolume")(270, "ActivePortIndex")(269, "Ports")(268, "CardIndex")(259, "ObjectName")(258, "PulseObject")(257, "Index")(263, "Muted")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 270 "ActivePortIndex" terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Program received signal SIGABRT, Aborted. [Switching to Thread 0x7fff25f73700 (LWP 6269)] 0x00007ffff13265f8 in raise () from /usr/lib/libc.so.6 Another crash report from GDB http://hastebin.com/agayapohox.hs Thanks for the report Brian. I've just tested against plasmashell 5.20.2 and I can't reproduce this issue. Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I'm setting status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks. 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! |