Bug 483134

Summary: Plasma crash on resume from sleep
Product: [Plasma] plasmashell Reporter: retired <pepko94>
Component: generic-crashAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: kde, nate, wolfit
Priority: NOR Keywords: drkonqi
Version: 5.27.10   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi

Description retired 2024-03-10 17:01:55 UTC 
Application: plasmashell (5.27.10)

Qt Version: 5.15.12
Frameworks Version: 5.115.0
Operating System: Linux 6.7.9-273-tkg-eevdf x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.10 [CoredumpBackend]

-- Information about the crash:
Plasmashell process crashes when my PC wakes up from suspend to RAM.
At least it recovers

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#5  QSGAreaAllocator::mergeNodeWithNeighbors (this=0x7ac434185ad0, node=0x7ac4341a8e40) at /usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/util/qsgareaallocator.cpp:194
#6  0x00007ac5c21a5997 in QSGAreaAllocator::deallocateInNode (this=this@entry=0x7ac434185ad0, pos=..., node=<optimized out>) at /usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/util/qsgareaallocator.cpp:178
#7  0x00007ac5c21a59db in QSGAreaAllocator::deallocate (this=this@entry=0x7ac434185ad0, rect=...) at /usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/util/qsgareaallocator.cpp:116
#8  0x00007ac5c21abb9c in QSGOpenGLAtlasTexture::AtlasBase::remove (t=0x7ac434425110, this=0x7ac434185ac0) at /usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/util/qsgopenglatlastexture.cpp:286
#9  QSGOpenGLAtlasTexture::TextureBase::~TextureBase (this=0x7ac434425110, this=<optimized out>) at /usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/util/qsgopenglatlastexture.cpp:516


The reporter indicates this bug may be a duplicate of or related to bug 480308.

Reported using DrKonqi
Comment 1 retired 2024-03-10 17:02:00 UTC 
Created attachment 166891 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Nate Graham 2024-03-11 21:52:12 UTC 
Looks GPU-related, deep in the QtQuick rendering stack. Can you upgrade to Plasma 6 (which used Qt 6) and see if it still happens? Thanks!
Comment 3 retired 2024-03-13 11:19:07 UTC 
Haven't encountered it on 6.0 yet, but wasn't 5.27 meant to be an LTS release?
Comment 4 Bug Janitor Service 2024-03-28 03:46:52 UTC 
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!
Comment 5 Bug Janitor Service 2024-04-12 03:48:01 UTC 
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!
Comment 6 Carl 2024-08-08 16:10:28 UTC 
I went to the store and left the system on. When I returned from shopping, the computer was asleep, I wiggled the mouse to wake it up and that is when the crash occurred. The system recovered from the crash successfully, but still reported it. There is no abnormal behavior.
Comment 7 Nate Graham 2024-08-13 19:04:11 UTC 

*** This bug has been marked as a duplicate of bug 414805 ***