Bug 473794 - Memory corruption crash when closing a notification
Summary: Memory corruption crash when closing a notification
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Notifications (other bugs)
Version First Reported In: 5.27.7
Platform: Neon Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-08-27 10:08 UTC by Oded Arbel
Modified: 2024-06-03 15:31 UTC (History)
4 users (show)

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


Attachments
DrKonqi crash data (48.79 KB, text/plain)
2023-08-27 10:08 UTC, Oded Arbel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Oded Arbel 2023-08-27 10:08:52 UTC
Created attachment 161207 [details]
DrKonqi crash data

SUMMARY

I believe I got this from closing a "panel was removed" plasma notification.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10
Kernel Version: 6.4.11-060411-generic (64-bit)
Graphics Platform: offscreen
Processors: 11 × Unknown Type, 9 × 12th Gen Intel® Core™ i7-12700H
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Comment 1 Nate Graham 2023-08-28 20:16:19 UTC
Pasting the relevant part of the backtrace inline for searchability:

#6  QString::QString(QString const&) (other=<error reading variable: Cannot access memory at address 0x10>, this=0x7ffc7abc1c78) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1093
#7  KNotification::xdgActivationToken() const (this=0x0) at ./src/knotification.cpp:649
#8  0x00007fe5f0396328 in  () at /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kded/networkmanagement.so
#9  0x00007fe628cf4924 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc7abc1d40, r=0x557763c79410, this=0x7fe620063f90) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#10 doActivate<false>(QObject*, int, void**) (sender=0x7fe620078350, signal_index=6, argv=0x7ffc7abc1d40) at kernel/qobject.cpp:3925
#11 0x00007fe628ced9f7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x7fe620078350, m=m@entry=0x7fe6245c8fc0 <KNotification::staticMetaObject>, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x0) at kernel/qobject.cpp:3985
#12 0x00007fe624590b77 in KNotification::action1Activated() (this=this@entry=0x7fe620078350) at ./obj-x86_64-linux-gnu/src/KF5Notifications_autogen/include/moc_knotification.cpp:583
#13 0x00007fe624593350 in KNotification::activate(unsigned int) (this=this@entry=0x7fe620078350, action=1) at ./src/knotification.cpp:334
#14 0x00007fe624595fc9 in KNotificationManager::notificationActivated(int, int) (this=0x7fe6245cb000 <(anonymous namespace)::Q_QGS_s_self::innerFunction()::holder>, id=<optimized out>, action=<optimized out>) at ./src/knotificationmanager.cpp:240
#15 0x00007fe628cf4924 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc7abc1f30, r=0x7fe6245cb000 <(anonymous namespace)::Q_QGS_s_self::innerFunction()::holder>, this=0x557763da1be0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#16 doActivate<false>(QObject*, int, void**) (sender=0x557763f56ff0, signal_index=4, argv=0x7ffc7abc1f30) at kernel/qobject.cpp:3925
#17 0x00007fe628ced9f7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=<optimized out>, m=<optimized out>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffc7abc1f30) at kernel/qobject.cpp:3985
#18 0x00007fe624599b83 in KNotificationPlugin::actionInvoked(int, int) (this=<optimized out>, _t1=<optimized out>, _t2=<optimized out>) at ./obj-x86_64-linux-gnu/src/KF5Notifications_autogen/include/moc_knotificationplugin.cpp:180

Looks like memory corruption, but the presence of plasma-nm in the backtrace is weird given that the notification closed to trigger this crash came from something other than plasma-nm.
Comment 2 Oded Arbel 2023-08-29 07:42:19 UTC
It could have been a network change notification - IIRC I had a few notifications at the same time, and the crashed happened a few seconds after closing the notification, then the crash dialog was sitting unattended for a while as I was dealing with more urgent stuff. I may be misremembering.
Comment 3 Akseli Lahtinen 2024-06-03 13:32:05 UTC
Have you encountered this on Plasma 6?
Comment 4 Oded Arbel 2024-06-03 15:31:16 UTC
I can't pretend to remember what this was about, and I'm now on Plasma 6 so if there is any indication that this crash is Plasma 5 specific - then I'm happy to let it go. If I get interesting crashes, I'll report them in a new ticket.