Bug 501027

Summary:	Crash happens frequently, but not often
Product:	[Plasma] plasmashell	Reporter:	m.wege
Component:	generic-crash	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	cwo.kde, mds_foss
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	6.3.2
Target Milestone:	1.0
Platform:	Neon
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=498246
Latest Commit:		Version Fixed In:
Sentry Crash Report:	https://crash-reports.kde.org/organizations/kde/issues/129998/events/6e90f6f1ff4146ff98237ea2ebcb48f6/
Attachments:	New crash information added by DrKonqi

Description m.wege 2025-03-03 22:16:09 UTC

Application: plasmashell (6.3.2)

ApplicationNotResponding [ANR]: false
Qt Version: 6.8.2
Frameworks Version: 6.11.0
Operating System: Linux 6.11.0-17-generic x86_64
Windowing System: Wayland
Distribution: KDE neon 6.3
DrKonqi: 6.3.2 [CoredumpBackend]

-- Information about the crash:
This crash happens frequently, but not often. I can not really tell the context, but I want to know, if it is related to bug 499383 which according to others only is related to a dual monitor setup. Because this crash happened without a 2. monitor attached.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#6  QScopedPointer<QObjectData, QScopedPointerDeleter<QObjectData> >::get (this=0x8) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qscopedpointer.h:110
[...]
#9  QObjectPrivate::get (o=0x0) at /usr/include/x86_64-linux-gnu/qt6/QtCore/6.8.2/QtCore/private/qobject_p.h:151
#10 QQmlData::get (object=0x0) at /usr/src/qt6-declarative-6.8.2-0zneon+24.04+noble+release+build35/src/qml/qml/qqmldata_p.h:233
#11 QQmlDelegateModelItem::destroyObject (this=0x5a82b3a7ebb0) at /usr/src/qt6-declarative-6.8.2-0zneon+24.04+noble+release+build35/src/qmlmodels/qqmldelegatemodel.cpp:2483
#12 0x00007725c1bdabc7 in QQmlDelegateModelPrivate::destroyCacheItem (this=0x5a82b16f0f30, cacheItem=0x5a82b3a7ebb0) at /usr/src/qt6-declarative-6.8.2-0zneon+24.04+noble+release+build35/src/qmlmodels/qqmldelegatemodel.cpp:614


Reported using DrKonqi

Comment 1 m.wege 2025-03-03 22:16:10 UTC

Created attachment 179090 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

Comment 2 cwo 2025-03-04 06:57:08 UTC

Thank you for the bug report! It does not seem to be related to  bug 499383, but we are tracking this kind of crash already in bug 491699. Unfortunately there is little we can say at this moment - the crash seems to happen deep in Qt processing far from any KDE code, but that doesn't mean it's necessarily not our fault. It's hard to investigate as only a small number of users seem to be affected and we have not found a way to explicitly trigger the issue yet-

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

Comment 3 cwo 2025-03-04 07:02:08 UTC

Hm, it also seems to be the same crash that you reported in bug 498246. There you said that removing  the  catwalk widget apparently fixed it. I take it that the crash came back even without that widget?

Comment 4 m.wege 2025-03-04 07:28:31 UTC

(In reply to cwo from comment #3)
> Hm, it also seems to be the same crash that you reported in bug 498246.
> There you said that removing  the  catwalk widget apparently fixed it. I
> take it that the crash came back even without that widget?
I was not aware it is the same crash. The cat walk crash happened extremely often, and removing that widget really bettered the situation. If this is really the same crash, then may be the fact, that removing the catwalk reduces the occurrence can give an indication of the cause?

Comment 5 cwo 2025-03-04 07:45:41 UTC

(In reply to m.wege from comment #4)
> I was not aware it is the same crash. The cat walk crash happened extremely
> often, and removing that widget really bettered the situation. If this is
> really the same crash, then may be the fact, that removing the catwalk
> reduces the occurrence can give an indication of the cause?

They look the same to me. It helps a little,  but still does not tell us much about what exactly causes Qt to get into a state where it crashes, only that something that this widget does in some situations seems to be related. And yours was the only report we had here that clearly involved this widget, so it does not seem to happen for all cat walk users. I'll add a comment to the other bug report in case it does help-

Comment 6 m.wege 2025-03-04 07:50:29 UTC

I might add, that I later found out that I still had been running the cat version which I had installed from KDE5, and it is had not been updated automatically since it was installed out of KDE store. That may be the cause that other cat walk users did not have the same crash.