[plasmashell] [Bug 428394] huge memory leak (Wayland session)
https://bugs.kde.org/show_bug.cgi?id=428394 --- Comment #16 from Bug Janitor Service --- 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! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak (Wayland session)
https://bugs.kde.org/show_bug.cgi?id=428394 --- Comment #15 from Germano Massullo --- (In reply to Nate Graham from comment #14) > Germano, can you confirm that? Today I will try to switch back to Wayland session and check if this bug still happens. It will require some days of testing -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak (Wayland session)
https://bugs.kde.org/show_bug.cgi?id=428394 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #14 from Nate Graham --- Germano, can you confirm that? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak (Wayland session)
https://bugs.kde.org/show_bug.cgi?id=428394 --- Comment #13 from Jiri Slaby --- (In reply to Jiri Slaby from comment #12) > (In reply to David Edmundson from comment #11) > > *** Bug 441213 has been marked as a duplicate of this bug. *** > > FTR I'd say it's gone now. I didn't have to kill plasma for at least a month > (I don't even remember when I had to last time). plasma5-session-5.23.4-1.4.noarch I have. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak (Wayland session)
https://bugs.kde.org/show_bug.cgi?id=428394 --- Comment #12 from Jiri Slaby --- (In reply to David Edmundson from comment #11) > *** Bug 441213 has been marked as a duplicate of this bug. *** FTR I'd say it's gone now. I didn't have to kill plasma for at least a month (I don't even remember when I had to last time). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak (Wayland session)
https://bugs.kde.org/show_bug.cgi?id=428394 David Edmundson changed: What|Removed |Added CC||jirisl...@gmail.com --- Comment #11 from David Edmundson --- *** Bug 441213 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak (Wayland session)
https://bugs.kde.org/show_bug.cgi?id=428394 Nate Graham changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak (Wayland session)
https://bugs.kde.org/show_bug.cgi?id=428394 Nate Graham changed: What|Removed |Added Component|general |generic-performance Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak (Wayland session)
https://bugs.kde.org/show_bug.cgi?id=428394 Germano Massullo changed: What|Removed |Added Version|5.20.1 |5.20.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak (Wayland session)
https://bugs.kde.org/show_bug.cgi?id=428394 --- Comment #10 from Germano Massullo --- (In reply to Germano Massullo from comment #8) > [...] (new Plasma version, see details below) [...] I am sorry I have forgotten to add Plasma KDE version plasma-desktop-5.20.3-1.fc33.x86_64 KDE Frameworks 5.75.0 Qt 5.15.1 (compilato con 5.15.1) Il sistema di finestre wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak (Wayland session)
https://bugs.kde.org/show_bug.cgi?id=428394 Germano Massullo changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #9 from Germano Massullo --- Setting status back to reported -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak (Wayland session)
https://bugs.kde.org/show_bug.cgi?id=428394 --- Comment #8 from Germano Massullo --- Created attachment 133294 --> https://bugs.kde.org/attachment.cgi?id=133294=edit heaptrack file heaptrack --analyze "/home/user/heaptrack.plasmashell.3791.zst" /usr/bin/heaptrack: riga 74: 5716 Errore di segmentazione (core dump created) "$EXE_PATH/heaptrack_gui" "$@" And this is the GDB trace that I got from drkonqi while triggering the problem. I must say that this time (new Plasma version, see details below) I did not get a big RAM usage, it always stayed in his normal RAM usage range Application: Plasma (plasmashell), signal: Aborted Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f5db79b8940 (LWP 3005))] [KCrash Handler] #6 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:49 #7 0x7f5dbb6ff8a4 in __GI_abort () at abort.c:79 #8 0x7f5dbbb22b07 in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #9 QMessageLogger::fatal (this=, msg=) at global/qlogging.cpp:893 #10 0x7f5daa393d89 in QtWaylandClient::QWaylandDisplay::checkError (this=) at qwaylanddisplay.cpp:209 #11 QtWaylandClient::QWaylandDisplay::checkError (this=) at qwaylanddisplay.cpp:204 #12 0x7f5daa3a23ee in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x55ecd3d8f110) at qwaylanddisplay.cpp:222 #13 0x7f5dbbd172a0 in doActivate (sender=0x55ecd3e004a0, signal_index=3, argv=0x7ffc6ff431b0) at kernel/qobject.cpp:3898 #14 0x7f5dbbd1a486 in QSocketNotifier::activated (this=this@entry=0x55ecd3e004a0, _t1=..., _t2=, _t3=...) at .moc/moc_qsocketnotifier.cpp:178 #15 0x7f5dbbd1abf9 in QSocketNotifier::event (this=0x55ecd3e004a0, e=0x7ffc6ff432d0) at kernel/qsocketnotifier.cpp:302 #16 0x7f5dbc8aa15f in QApplicationPrivate::notify_helper (this=, receiver=0x55ecd3e004a0, e=0x7ffc6ff432d0) at kernel/qapplication.cpp:3630 #17 0x7f5dbbce8bf8 in QCoreApplication::notifyInternal2 (receiver=0x55ecd3e004a0, event=0x7ffc6ff432d0) at kernel/qcoreapplication.cpp:1063 #18 0x7f5dbbd3444f in socketNotifierSourceDispatch (source=source@entry=0x55ecd3dc17a0) at kernel/qeventdispatcher_glib.cpp:107 #19 0x7f5dba28dfd7 in g_main_dispatch (context=0x55ecd3de53f0) at ../glib/gmain.c:3325 #20 g_main_context_dispatch (context=0x55ecd3de53f0) at ../glib/gmain.c:4016 #21 0x7f5dba2ded88 in g_main_context_iterate.constprop.0 (context=context@entry=0x55ecd3de53f0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4092 #22 0x7f5dba28b41f in g_main_context_iteration (context=0x55ecd3de53f0, may_block=1) at ../glib/gmain.c:4157 #23 0x7f5dbbd33a2f in QEventDispatcherGlib::processEvents (this=0x55ecd3e00300, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #24 0x7f5dbbce765b in QEventLoop::exec (this=0x7ffc6ff434e0, flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #25 0x7f5dbbcef020 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #26 0x55ecd34c87ca in main (argc=, argv=0x7ffc6ff43700) at /usr/src/debug/plasma-workspace-5.20.3-2.fc33.x86_64/shell/main.cpp:252 [Inferior 1 (process 3005) detached] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak (Wayland session)
https://bugs.kde.org/show_bug.cgi?id=428394 --- Comment #7 from Bug Janitor Service --- 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! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak (Wayland session)
https://bugs.kde.org/show_bug.cgi?id=428394 --- Comment #6 from Germano Massullo --- (In reply to David Edmundson from comment #5) > Why do you suspect that? Because I remember starting to get massive I/O from disk after having tried to use it. Just a hypothesis -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak (Wayland session)
https://bugs.kde.org/show_bug.cgi?id=428394 --- Comment #5 from David Edmundson --- Why do you suspect that? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak (Wayland session)
https://bugs.kde.org/show_bug.cgi?id=428394 --- Comment #4 from Germano Massullo --- I really suspect it may be related to https://bugs.kde.org/show_bug.cgi?id=428409 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak (Wayland session)
https://bugs.kde.org/show_bug.cgi?id=428394 --- Comment #3 from Germano Massullo --- (In reply to Justin Zobel from comment #2) > (In reply to Germano Massullo from comment #1) > > unfortunately heaptrack was not able to save anything, probably due lack of > > free RAM > > Are you able to monitor your session after restarting and try get a > heaptrack as it's getting close to consuming your RAM? I will try triggering it again -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak (Wayland session)
https://bugs.kde.org/show_bug.cgi?id=428394 Justin Zobel changed: What|Removed |Added CC||justin.zo...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Justin Zobel --- (In reply to Germano Massullo from comment #1) > unfortunately heaptrack was not able to save anything, probably due lack of > free RAM Are you able to monitor your session after restarting and try get a heaptrack as it's getting close to consuming your RAM? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak (Wayland session)
https://bugs.kde.org/show_bug.cgi?id=428394 --- Comment #1 from Germano Massullo --- unfortunately heaptrack was not able to save anything, probably due lack of free RAM -- You are receiving this mail because: You are watching all bug changes.
