Bug 418767 - Plasma crashes repeatedly in Plasma::WindowThumbnail::WindowThumbnail()
Summary: Plasma crashes repeatedly in Plasma::WindowThumbnail::WindowThumbnail()
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: master
Platform: openSUSE Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-12 06:10 UTC by Pavel Florian
Modified: 2023-09-08 03:45 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Backtrace file (31.93 KB, text/plain)
2020-03-12 06:10 UTC, Pavel Florian
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Florian 2020-03-12 06:10:52 UTC
Created attachment 126738 [details]
Backtrace file

SUMMARY
The Plasma crashes are repeatedly andrandomly repeatedly and critical!
I used the Firefox Browser. I searched in google Page. Next used applications were Gt Creator, Dolphin and KMail.
Before the crash were GUIs of applications and plasma shell frozen.

STEPS TO REPRODUCE


OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 David Edmundson 2020-04-07 09:13:01 UTC
Pasting inline:

#5  0x00007f37c6fd8ac6 in Plasma::WindowThumbnail::WindowThumbnail (parent=0x0, this=0x55a90c99cc20) at /usr/include/c++/9/bits/atomic_base.h:326
#6  QQmlPrivate::QQmlElement<Plasma::WindowThumbnail>::QQmlElement (this=0x55a90c99cc20) at /usr/include/qt5/QtQml/qqmlprivate.h:106
#7  QQmlPrivate::createInto<Plasma::WindowThumbnail> (memory=0x55a90c99cc20) at /usr/include/qt5/QtQml/qqmlprivate.h:127
#8  0x00007f37daef9aac in QQmlType::create (this=this@entry=0x7ffe34b668b0, out=out@entry=0x7ffe34b668a8, memory=memory@entry=0x7ffe34b668b8, additionalMemory=additionalMemory@entry=144) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-1.3.x86_64/src/qml/qml/qqmltype.cpp:485
#9  0x00007f37daf55bc0 in QQmlObjectCreator::createInstance (this=0x7ffe34b67980, index=22, parent=0x55a90afbe750, isContextObject=<optimized out>) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-1.3.x86_64/src/qml/qml/qqmlobjectcreator.cpp:1203
#10 0x00007f37daf54516 in QQmlObjectCreator::setPropertyBinding (this=0x7ffe34b67980, bindingProperty=0x7f37c007ed28, binding=0x7f37af69b3cc) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-1.3.x86_64/src/qml/qml/qqmlobjectcreator.cpp:861
Comment 2 chenlinux945 2020-04-07 09:13:56 UTC
I dont use Google Page, Firefox and Gt Creator but I've got a similar bug : https://bugs.kde.org/show_bug.cgi?id=419420
Comment 3 David Edmundson 2020-04-07 09:15:58 UTC
That backtrace itself doesnt' make any sense. The constructor doesn't line up with the filename.

Also crashes inside QQmlElement are odd.


You say it crashes repeatedly. Can you confirm if the backtraces are the same.
Is memory also skyroketting when in use?

>Before the crash were GUIs of applications and plasma shell frozen.

plasmashell shouldn't affect the state of GUIs. Can you elaborate? Was firefox  frozen?
Comment 4 Pavel Florian 2020-04-07 17:20:41 UTC
The Plasma was logged out repeatedly and randomly. The Backtraces were very similar (with Qt calling in crashed threads),  before it was GUI Frozen. Firefox was one of frozen applications.
When I discovered this error there was too commonly noise on parts of display. It suggests, that it may be problem with  Intel Graphics cards drivers.
Comment 5 Pavel Florian 2020-04-07 17:26:27 UTC
(In reply to chenlinux2 from comment #2)
> I dont use Google Page, Firefox and Gt Creator but I've got a similar bug :
> https://bugs.kde.org/show_bug.cgi?id=419420

This is the same bug.
Comment 6 David Edmundson 2020-04-07 20:27:02 UTC
It is not the same bug. The traces are completely different
Comment 7 Pavel Florian 2020-04-08 11:30:53 UTC
(In reply to David Edmundson from comment #6)
> It is not the same bug. The traces are completely different

Yes, the backtraces are different  too on my computer. However the problem has very similar manifesting and in backtraces are 3D accelerated parts of Qt and on my computer this problem has begun too upgrade of plasma shell.
Due to facts, that I have too 15.6 Display on my notebook, different backtraces and noise on the display, I think, that these problems was probably caused by bad response of Intel graphics cards drivers.
After last Tumbleweed upgrade (202000331, with MESA upgrade) is the problem not actual for me. :)
Comment 8 Pavel Florian 2020-04-14 10:10:24 UTC
(In reply to Pavel Florian from comment #7)
> (In reply to David Edmundson from comment #6)
> > It is not the same bug. The traces are completely different
> 
> Yes, the backtraces are different  too on my computer. However the problem
> has very similar manifesting and in backtraces are 3D accelerated parts of
> Qt and on my computer this problem has begun too upgrade of plasma shell.
> Due to facts, that I have too 15.6 Display on my notebook, different
> backtraces and noise on the display, I think, that these problems was
> probably caused by bad response of Intel graphics cards drivers.
Comment 9 Pavel Florian 2020-04-14 10:15:02 UTC
Update: this bug appears again, but not so often.
Comment 10 Pavel Florian 2020-04-22 10:16:27 UTC
The Opensuse Thumbleweed  20200417 is generally stabil and this bug is performed only by occasionally GUI frozening for few seconds and by unwanted logouts in first three runs of my computer after software upgrade.
Comment 11 Noah Davis 2023-08-09 16:06:47 UTC
Is this still an issue with Plasma 5.27? I have not encountered anything like this with 5.26.1 or 5.27.5 and I don't have any steps to reproduce the bug.
Comment 12 Bug Janitor Service 2023-08-24 03:45:26 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 13 Bug Janitor Service 2023-09-08 03:45:22 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!