[plasmashell] [Bug 465326] Plasma crashes when opening kickoff, after freezing for a bit

2023-02-11 Thread Oliver Hiorns
https://bugs.kde.org/show_bug.cgi?id=465326

--- Comment #17 from Oliver Hiorns  ---
MR 2609 should fix this, no need to reproduce any more.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 465326] Plasma crashes when opening kickoff, after freezing for a bit

2023-02-11 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=465326

--- Comment #16 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2609

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 465326] Plasma crashes when opening kickoff, after freezing for a bit

2023-02-11 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=465326

osh...@eliyahu.co.uk changed:

   What|Removed |Added

 CC||osh...@eliyahu.co.uk

--- Comment #15 from osh...@eliyahu.co.uk ---
If you can reproduce this again, could you keep the system monitor open and
watch memory usage?

It seems like the crash might be caused by the system running out of memory,
and the freeze-up is because of an infinite loop that keeps trying to save the
same image again and again to the save file (in memory - it crashes before it
gets committed to disk).

So, if the theory is correct, while it is frozen, memory usage will increase
steadily, and when you run out of memory then it will crash. Being able to
confirm this would be good.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 465326] Plasma crashes when opening kickoff, after freezing for a bit

2023-02-11 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=465326

Fushan Wen  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=465603

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 465326] Plasma crashes when opening kickoff, after freezing for a bit

2023-02-11 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=465326

Bug Janitor Service  changed:

   What|Removed |Added

 Status|REPORTED|ASSIGNED
 Ever confirmed|0   |1

--- Comment #14 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2608

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 465326] Plasma crashes when opening kickoff, after freezing for a bit

2023-02-11 Thread Oded Arbel
https://bugs.kde.org/show_bug.cgi?id=465326

--- Comment #13 from Oded Arbel  ---
And now it is frozen on:

Thread 1 (Thread 0x7fe0605689c0 (LWP 13998) "plasmashell"):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7fe064acea65 in QtLinuxFutex::_q_futex(int*, int, int, unsigned long
long, int*, int) (val3=0, addr2=0x0, val2=0, val=3, op=0, addr=0x561a5ba91628)
at thread/qfutex_p.h:114
#2  QtLinuxFutex::futexWait
>(QBasicAtomicPointer&, QBasicAtomicPointer::Type)
(expectedValue=0x3, futex=...) at thread/qfutex_p.h:133
#3  lockInternal_helper (timeout=-1, elapsedTimer=0x0, d_ptr=...) at
thread/qmutex_linux.cpp:142
#4  QBasicMutex::lockInternal() (this=0x561a5ba91628) at
thread/qmutex_linux.cpp:159
#5  0x7fe064aced73 in QBasicMutex::lock() (this=0x561a5ba91628) at
thread/qmutex.h:84
#6  QRecursiveMutexPrivate::lock(int) (this=0x561a5ba91610,
timeout=timeout@entry=-1) at thread/qmutex.cpp:780
#7  0x7fe064acec69 in QMutex::lock() (this=this@entry=0x561a5ba94ed0) at
thread/qmutex.cpp:235
#8  0x7fdfb7b35100 in QMutexLocker::QMutexLocker(QBasicMutex*)
(m=0x561a5ba94ed0, this=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmutex.h:257
#9  QMutexLocker::QMutexLocker(QRecursiveMutex*) (m=0x561a5ba94ed0,
this=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmutex.h:262
#10 HistoryModel::insert(std::shared_ptr) (this=0x561a5ba94eb0,
item=std::shared_ptr (use count 3, weak count 0) = {...}) at
./klipper/historymodel.cpp:135
#11 0x7fdfb7b300d2 in History::insert(std::shared_ptr)
(this=, item=std::shared_ptr (use count 3, weak
count 0) = {...}) at ./klipper/history.cpp:95
#12 0x7fdfb7b1a166 in Klipper::applyClipChanges(QMimeData const*)
(this=this@entry=0x561a5ba66940, clipData=clipData@entry=0x561a61f5eb20) at
./klipper/klipper.cpp:687
#13 0x7fdfb7b1ca48 in Klipper::checkClipData(bool) (this=0x561a5ba66940,
selectionMode=) at ./klipper/klipper.cpp:828
#14 0x7fe064cf40d4 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffdab7519e0, r=0x561a5ba66940, this=0x561a5ba94dd0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#15 doActivate(QObject*, int, void**) (sender=0x561a5ba95010,
signal_index=3, argv=0x7ffdab7519e0) at kernel/qobject.cpp:3923
#16 0x7fe0644240a2 in KSystemClipboard::changed(QClipboard::Mode) () at
/lib/x86_64-linux-gnu/libKF5GuiAddons.so.5
#17 0x7fe064cf40d4 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffdab751a90, r=0x561a5ba95010, this=0x561a5ba85eb0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#18 doActivate(QObject*, int, void**) (sender=0x561a59946e80,
signal_index=3, argv=0x7ffdab751a90) at kernel/qobject.cpp:3923
#19 0x7fe066495e2e in ffi_call_unix64 () at ../src/x86/unix64.S:105
#20 0x7fe066492493 in ffi_call_int (cif=, fn=, rvalue=, avalue=, closure=)
at ../src/x86/ffi64.c:672
#21 0x7fe067088b20 in  () at /lib/x86_64-linux-gnu/libwayland-client.so.0
#22 0x7fe0670892c3 in  () at /lib/x86_64-linux-gnu/libwayland-client.so.0
#23 0x7fe0670894bc in wl_display_dispatch_queue_pending () at
/lib/x86_64-linux-gnu/libwayland-client.so.0
#24 0x7fe06652338a in QtWaylandClient::QWaylandDisplay::flushRequests()
(this=) at ./src/client/qwaylanddisplay.cpp:253
#25 0x7fe064ce9ade in QObject::event(QEvent*) (this=0x561a5992cb50,
e=0x7fe05400be20) at kernel/qobject.cpp:1347
#26 0x7fe06596c793 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x561a5992cb50, e=0x7fe05400be20) at
kernel/qapplication.cpp:3640
#27 0x7fe064cbc07a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x561a5992cb50, event=0x7fe05400be20) at
kernel/qcoreapplication.cpp:1064
#28 0x7fe064cbf167 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x561a59903ec0) at
kernel/qcoreapplication.cpp:1821
#29 0x7fe064d16487 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x561a59945d60) at kernel/qeventdispatcher_glib.cpp:277
#30 0x7fe0637bb569 in g_main_dispatch (context=0x7fe058005010) at
../../../glib/gmain.c:3444
#31 g_main_context_dispatch (context=0x7fe058005010) at
../../../glib/gmain.c:4162
#32 0x7fe0638103c8 in g_main_context_iterate.constprop.0
(context=0x7fe058005010, block=, dispatch=1, self=) at ../../../glib/gmain.c:4238
#33 0x7fe0637b8d20 in g_main_context_iteration (context=0x7fe058005010,
may_block=1) at ../../../glib/gmain.c:4303
#34 0x7fe064d15ad8 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x561a5994ab70, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#35 0x7fe064cba99b in
QEventLoop::exec(QFlags)
(this=this@entry=0x7ffdab752250, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#36 0x7fe064cc2f34 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#37 0x7fe0651364d0 in QGuiApplication::exec() () at
kernel/qguiapplication.cpp:187

[plasmashell] [Bug 465326] Plasma crashes when opening kickoff, after freezing for a bit

2023-02-11 Thread Oded Arbel
https://bugs.kde.org/show_bug.cgi?id=465326

--- Comment #12 from Oded Arbel  ---
BTW, it happened again yesterday (while I was away from the computer);

Feb 10 18:54:04 vesho plasmashell[3480]: libpng error: Write Error
Feb 10 18:54:04 vesho plasmashell[3480]: QBuffer::writeData: Memory allocation
error
Feb 10 18:54:04 vesho plasmashell[3480]: libpng error: Write Error
Feb 10 18:54:04 vesho plasmashell[3480]: QBuffer::writeData: Memory allocation
error
Feb 10 18:54:04 vesho plasmashell[3480]: libpng error: Write Error
Feb 10 18:54:04 vesho plasmashell[3480]: QBuffer::writeData: Memory allocation
error
Feb 10 18:54:04 vesho plasmashell[3480]: libpng error: Write Error
Feb 10 18:54:04 vesho plasmashell[3480]: QBuffer::writeData: Memory allocation
error
Feb 10 18:54:04 vesho plasmashell[3480]: libpng error: Write Error
Feb 10 18:54:04 vesho plasmashell[3480]: Qt Concurrent has caught an exception
thrown from a worker thread.
 This is not supported, exceptions
thrown in worker threads must be
 caught before control returns to Qt
Concurrent.
Feb 10 18:54:04 vesho plasmashell[3480]: terminate called after throwing an
instance of 'std::bad_alloc'
Feb 10 18:54:04 vesho plasmashell[3480]:   what():  std::bad_alloc
Feb 10 18:54:04 vesho plasmashell[3480]: 25 -- exe=/usr/bin/plasmashell
Feb 10 18:54:04 vesho plasmashell[3480]: 17 -- platform=wayland
Feb 10 18:54:04 vesho plasmashell[3480]: 20 -- appname=plasmashell
Feb 10 18:54:04 vesho plasmashell[3480]: 17 -- apppath=/usr/bin
Feb 10 18:54:04 vesho plasmashell[3480]: 9 -- signal=6
Feb 10 18:54:04 vesho plasmashell[3480]: 9 -- pid=3480
Feb 10 18:54:04 vesho plasmashell[3480]: 19 -- appversion=5.27.80
Feb 10 18:54:04 vesho plasmashell[3480]: 19 -- programname=Plasma
Feb 10 18:54:04 vesho plasmashell[3480]: 31 -- bugaddress=sub...@bugs.kde.org
Feb 10 18:54:04 vesho plasmashell[3480]: KCrash: crashing...
crashRecursionCounter = 2
Feb 10 18:54:04 vesho plasmashell[3480]: KCrash: Application Name = plasmashell
path = /usr/bin pid = 3480
Feb 10 18:54:04 vesho plasmashell[3480]: KCrash: Arguments:
/usr/bin/plasmashell --no-respawn

And this was after I cleared the clipboard history and copied some new images
into it - which didn't allow me to immediately reproduce the crash. Maybe it
needs some rest time to reproduce... I'll try to build with the merge request
next (but not today).

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 465326] Plasma crashes when opening kickoff, after freezing for a bit

2023-02-10 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=465326

--- Comment #11 from Fushan Wen  ---
This commit seems suspicious:
https://invent.kde.org/plasma/plasma-workspace/-/commit/f13501b42c015df5e2c727fd23a8731e9801e758

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 465326] Plasma crashes when opening kickoff, after freezing for a bit

2023-02-10 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=465326

Fushan Wen  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=464828
 CC||qydwhotm...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 465326] Plasma crashes when opening kickoff, after freezing for a bit

2023-02-10 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=465326

Fushan Wen  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=465225

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 465326] Plasma crashes when opening kickoff, after freezing for a bit

2023-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=465326

--- Comment #10 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2607

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 465326] Plasma crashes when opening kickoff, after freezing for a bit

2023-02-09 Thread Oded Arbel
https://bugs.kde.org/show_bug.cgi?id=465326

Oded Arbel  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
  Component|generic-performance |Clipboard
 Status|NEEDSINFO   |REPORTED

--- Comment #9 from Oded Arbel  ---
I believe the issue is that klipper is having a real hard time managing images
in the clipboard history (I had to screenshot followed by copy and paste a lot
last week), to the point of crashing plasmashell (which begs the question, BTW,
why is it running on plasmashell's main thread - it used to be a standalone
application). I tried to clear the clipboard history using the clipboard panel
widget's "clear" button, after which plasmashell froze for some minutes (!!)
with this trace:

---8<---
Thread 1 (Thread 0x7f86339a19c0 (LWP 885456) "plasmashell"):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f8637ecea65 in QtLinuxFutex::_q_futex(int*, int, int, unsigned long
long, int*, int) (val3=0, addr2=0x0, val2=0, val=3, op=0, addr=0x5601db2ee2f8)
at thread/qfutex_p.h:114
#2  QtLinuxFutex::futexWait
>(QBasicAtomicPointer&, QBasicAtomicPointer::Type)
(expectedValue=0x3, futex=...) at thread/qfutex_p.h:133
#3  lockInternal_helper (timeout=-1, elapsedTimer=0x0, d_ptr=...) at
thread/qmutex_linux.cpp:142
#4  QBasicMutex::lockInternal() (this=0x5601db2ee2f8) at
thread/qmutex_linux.cpp:159
#5  0x7f8637eced73 in QBasicMutex::lock() (this=0x5601db2ee2f8) at
thread/qmutex.h:84
#6  QRecursiveMutexPrivate::lock(int) (this=0x5601db2ee2e0,
timeout=timeout@entry=-1) at thread/qmutex.cpp:780
#7  0x7f8637ecec69 in QMutex::lock() (this=this@entry=0x5601db2eed00) at
thread/qmutex.cpp:235
#8  0x7f858e6a1f67 in QMutexLocker::QMutexLocker(QBasicMutex*)
(m=0x5601db2eed00, this=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmutex.h:257
#9  QMutexLocker::QMutexLocker(QRecursiveMutex*) (m=0x5601db2eed00,
this=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmutex.h:262
#10 HistoryModel::clear() (this=0x5601db2eece0) at
./klipper/historymodel.cpp:26
#11 0x7f858e69e1fd in History::slotClear() (this=) at
./klipper/history.cpp:113
#12 0x7f858e68fe85 in Klipper::slotAskClearHistory() (this=0x5601dbe262a0)
at ./klipper/klipper.h:83
#13 0x7f858e680ef9 in ClipboardJob::start() (this=0x5601e3718180) at
./klipper/clipboardjob.cpp:38
#14 0x7f86380e9ade in QObject::event(QEvent*) (this=0x5601e3718180,
e=0x5601e3711ff0) at kernel/qobject.cpp:1347
#15 0x7f8638d6c793 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x5601e3718180, e=0x5601e3711ff0) at
kernel/qapplication.cpp:3640
#16 0x7f86380bc07a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x5601e3718180, event=0x5601e3711ff0) at
kernel/qcoreapplication.cpp:1064
#17 0x7f86380bf167 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x5601d95baec0) at
kernel/qcoreapplication.cpp:1821
#18 0x7f8638116487 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x5601d95fcce0) at kernel/qeventdispatcher_glib.cpp:277
#19 0x7f8636bec569 in g_main_dispatch (context=0x7f862c005010) at
../../../glib/gmain.c:3444
#20 g_main_context_dispatch (context=0x7f862c005010) at
../../../glib/gmain.c:4162
#21 0x7f8636c413c8 in g_main_context_iterate.constprop.0
(context=0x7f862c005010, block=, dispatch=1, self=) at ../../../glib/gmain.c:4238
#22 0x7f8636be9d20 in g_main_context_iteration (context=0x7f862c005010,
may_block=1) at ../../../glib/gmain.c:4303
#23 0x7f8638115ad8 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x5601d960f1c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#24 0x7f86380ba99b in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fff31294ef0, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#25 0x7f86380c2f34 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#26 0x7f86385364d0 in QGuiApplication::exec() () at
kernel/qguiapplication.cpp:1870
#27 0x7f8638d6c709 in QApplication::exec() () at
kernel/qapplication.cpp:2832
#28 0x5601d79e2a8b in main(int, char**) (argc=,
argv=) at ./shell/main.cpp:235
---8<---

and then crashed with the same 'std::bad_alloc' uncaught exception (while the
main thread is still stuck on the above trace).

After restarting, I can still see plasmashell freezing on
HistoryModel::insert() for long stretches of time. I removed
~/.local/share/klipper/history2.lst and SIGKILLed plasmashell, and now it is
behaving much better, as well as a lot of klipper problems I had are now no
longer exhibiting.

I need to run it a bit longer to make sure, but even copying and pasting images
seem to work fine now.

I have the copy of the klipper history file that was apparently giving me
grief, if som

[plasmashell] [Bug 465326] Plasma crashes when opening kickoff, after freezing for a bit

2023-02-09 Thread Oded Arbel
https://bugs.kde.org/show_bug.cgi?id=465326

--- Comment #8 from Oded Arbel  ---
Huh, apparently I needed to look at the logs:

---8<---
Feb 09 12:42:03 vesho plasmashell[871706]: QBuffer::writeData: Memory
allocation error
Feb 09 12:42:03 vesho plasmashell[871706]: libpng error: Write Error
# the above two lines repeat many times...
Feb 09 12:42:03 vesho plasmashell[871706]: QBuffer::writeData: Memory
allocation error
Feb 09 12:42:03 vesho plasmashell[871706]: libpng error: Write Error
Feb 09 12:42:03 vesho plasmashell[871706]: Qt Concurrent has caught an
exception thrown from a worker thread.
   This is not supported, exceptions
thrown in worker threads must be
   caught before control returns to Qt
Concurrent.
Feb 09 12:42:03 vesho plasmashell[871706]: terminate called after throwing an
instance of 'std::bad_alloc'
Feb 09 12:42:03 vesho plasmashell[871706]:   what():  std::bad_alloc
Feb 09 12:42:03 vesho plasmashell[871706]: 25 -- exe=/usr/bin/plasmashell
Feb 09 12:42:03 vesho plasmashell[871706]: 17 -- platform=wayland
Feb 09 12:42:03 vesho plasmashell[871706]: 20 -- appname=plasmashell
Feb 09 12:42:03 vesho plasmashell[871706]: 17 -- apppath=/usr/bin
Feb 09 12:42:03 vesho plasmashell[871706]: 9 -- signal=6
Feb 09 12:42:03 vesho plasmashell[871706]: 11 -- pid=871706
Feb 09 12:42:03 vesho plasmashell[871706]: 19 -- appversion=5.27.80
Feb 09 12:42:03 vesho plasmashell[871706]: 19 -- programname=Plasma
Feb 09 12:42:03 vesho plasmashell[871706]: 31 -- bugaddress=sub...@bugs.kde.org
---8<---

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 465326] Plasma crashes when opening kickoff, after freezing for a bit

2023-02-08 Thread Oded Arbel
https://bugs.kde.org/show_bug.cgi?id=465326

--- Comment #7 from Oded Arbel  ---
This crash still happens after tonight's neon unstable updates. I think it is
definitely related to klipper's HistoryModel::insert() operation: something in
the mutex there is causing an issue - if we look at the last (first?) 2 threads
from the stack trace (appended here is a new one from just about now), we can
see that "Thread 1" (LWP 585125) is not the main thread (like it is in most
back traces), its just a thread that was created to invoke qTerminate(), while
the main thread is "Thread 2"  (which has the earlier LWP id 550212) - and that
one is blocking in HistoryModel::insert(). This is also where plasmashell gets
stuck when it freezes on me - like it is right now, and then it crashed. Maybe
it is some kind of watchdog?

I tried to look at what could be deadlocking with the HistoryModel::insert()
mutex but (a) when backtracing a frozen plasmashell, I don't see anything else
holding a QMutexLocker, and (b) looking at the source code I can see that
HistoryModel exposes a pointer to its mutex using a public accessor, so anyone
can be locking it 🤷🤦.

Here's the last 2 threads from the (one of) the new crash:

Thread 2 (Thread 0x7fbc546629c0 (LWP 550212)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7fbc56ecea65 in QtLinuxFutex::_q_futex(int*, int, int, unsigned long
long, int*, int) (val3=0, addr2=0x0, val2=0, val=3, op=0, addr=0x564becec7268)
at thread/qfutex_p.h:114
#2  QtLinuxFutex::futexWait
>(QBasicAtomicPointer&, QBasicAtomicPointer::Type)
(expectedValue=0x3, futex=...) at thread/qfutex_p.h:133
#3  lockInternal_helper (timeout=-1, elapsedTimer=0x0, d_ptr=...) at
thread/qmutex_linux.cpp:142
#4  QBasicMutex::lockInternal() (this=0x564becec7268) at
thread/qmutex_linux.cpp:159
#5  0x7fbc56eced73 in QBasicMutex::lock() (this=0x564becec7268) at
thread/qmutex.h:84
#6  QRecursiveMutexPrivate::lock(int) (this=0x564becec7250,
timeout=timeout@entry=-1) at thread/qmutex.cpp:780
#7  0x7fbc56ecec69 in QMutex::lock() (this=this@entry=0x564becec6fd0) at
thread/qmutex.cpp:235
#8  0x7fbbec059100 in QMutexLocker::QMutexLocker(QBasicMutex*)
(m=0x564becec6fd0, this=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmutex.h:257
#9  QMutexLocker::QMutexLocker(QRecursiveMutex*) (m=0x564becec6fd0,
this=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmutex.h:262
#10 HistoryModel::insert(std::shared_ptr) (this=0x564becec6fb0,
item=std::shared_ptr (use count 3, weak count 0) = {...}) at
./klipper/historymodel.cpp:135
#11 0x7fbbec0540d2 in History::insert(std::shared_ptr)
(this=, item=std::shared_ptr (use count 3, weak
count 0) = {...}) at ./klipper/history.cpp:95
#12 0x7fbbec03e166 in Klipper::applyClipChanges(QMimeData const*)
(this=this@entry=0x564bec263290, clipData=clipData@entry=0x564bf149c600) at
./klipper/klipper.cpp:687
#13 0x7fbbec040a48 in Klipper::checkClipData(bool) (this=0x564bec263290,
selectionMode=) at ./klipper/klipper.cpp:828
#14 0x7fbc570f40d4 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fffd0088e60, r=0x564bec263290, this=0x564becec6ad0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#15 doActivate(QObject*, int, void**) (sender=0x564becec72b0,
signal_index=3, argv=0x7fffd0088e60) at kernel/qobject.cpp:3923
#16 0x7fbc5650d0a2 in KSystemClipboard::changed(QClipboard::Mode) () at
/lib/x86_64-linux-gnu/libKF5GuiAddons.so.5
#17 0x7fbc570f40d4 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fffd0088f10, r=0x564becec72b0, this=0x564becebf980) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#18 doActivate(QObject*, int, void**) (sender=0x564beaa64de0,
signal_index=3, argv=0x7fffd0088f10) at kernel/qobject.cpp:3923
#19 0x7fbc58aa9e2e in ffi_call_unix64 () at ../src/x86/unix64.S:105
#20 0x7fbc58aa6493 in ffi_call_int (cif=, fn=, rvalue=, avalue=, closure=)
at ../src/x86/ffi64.c:672
#21 0x7fbc59561b20 in  () at /lib/x86_64-linux-gnu/libwayland-client.so.0
#22 0x7fbc595622c3 in  () at /lib/x86_64-linux-gnu/libwayland-client.so.0
#23 0x7fbc595624bc in wl_display_dispatch_queue_pending () at
/lib/x86_64-linux-gnu/libwayland-client.so.0
#24 0x7fbc5852338a in QtWaylandClient::QWaylandDisplay::flushRequests()
(this=) at ./src/client/qwaylanddisplay.cpp:253
#25 0x7fbc570e9ade in QObject::event(QEvent*) (this=0x564beaa4ab50,
e=0x7fbc48008100) at kernel/qobject.cpp:1347
#26 0x7fbc57d6c793 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x564beaa4ab50, e=0x7fbc48008100) at
kernel/qapplication.cpp:3640
#27 0x7fbc570bc07a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x564beaa4ab50, event=0x7fbc48008100) at
kernel/qcoreapplication.cpp:1064
#28 0x7fbc570bf167 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x564beaa21ec0) at
kernel/qcoreapplication.cpp:1821
#29 0x7f

[plasmashell] [Bug 465326] Plasma crashes when opening kickoff, after freezing for a bit

2023-02-07 Thread Oded Arbel
https://bugs.kde.org/show_bug.cgi?id=465326

--- Comment #6 from Oded Arbel  ---
The current behavior (after all today's updates) is that the crash happens
frequently while I'm doing other things, regardless of interaction with the
shell itself, so its hard for me to catch it. But the shell does freeze quite a
lot - at which point plasmashell uses 100% of a core - and if I capture the
backtrace while it happens, the main thread looks like this:

Thread 1 (Thread 0x7f108992f9c0 (LWP 36226) "plasmashell"):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f108dccea65 in QtLinuxFutex::_q_futex(int*, int, int, unsigned long
long, int*, int) (val3=0, addr2=0x0, val2=0, val=3, op=0, addr=0x560684982d48)
at thread/qfutex_p.h:114
#2  QtLinuxFutex::futexWait
>(QBasicAtomicPointer&, QBasicAtomicPointer::Type)
(expectedValue=0x3, futex=...) at thread/qfutex_p.h:133
#3  lockInternal_helper (timeout=-1, elapsedTimer=0x0, d_ptr=...) at
thread/qmutex_linux.cpp:142
#4  QBasicMutex::lockInternal() (this=0x560684982d48) at
thread/qmutex_linux.cpp:159
#5  0x7f108dcced73 in QBasicMutex::lock() (this=0x560684982d48) at
thread/qmutex.h:84
#6  QRecursiveMutexPrivate::lock(int) (this=0x560684982d30,
timeout=timeout@entry=-1) at thread/qmutex.cpp:780
#7  0x7f108dccec69 in QMutex::lock() (this=this@entry=0x560684983270) at
thread/qmutex.cpp:235
#8  0x7f10041ef100 in QMutexLocker::QMutexLocker(QBasicMutex*)
(m=0x560684983270, this=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmutex.h:257
#9  QMutexLocker::QMutexLocker(QRecursiveMutex*) (m=0x560684983270,
this=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmutex.h:262
#10 HistoryModel::insert(std::shared_ptr) (this=0x560684983250,
item=std::shared_ptr (use count 3, weak count 0) = {...}) at
./klipper/historymodel.cpp:135
#11 0x7f10041ea0d2 in History::insert(std::shared_ptr)
(this=, item=std::shared_ptr (use count 3, weak
count 0) = {...}) at ./klipper/history.cpp:95
#12 0x7f10041d4166 in Klipper::applyClipChanges(QMimeData const*)
(this=this@entry=0x5606836c9840, clipData=clipData@entry=0x560688d5a8f0) at
./klipper/klipper.cpp:687
#13 0x7f10041d6a48 in Klipper::checkClipData(bool) (this=0x5606836c9840,
selectionMode=) at ./klipper/klipper.cpp:828
#14 0x7f108def40d4 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffc7a38d1e0, r=0x5606836c9840, this=0x560684982f70) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#15 doActivate(QObject*, int, void**) (sender=0x560684983020,
signal_index=3, argv=0x7ffc7a38d1e0) at kernel/qobject.cpp:3923
#16 0x7f108d6230a2 in KSystemClipboard::changed(QClipboard::Mode) () at
/lib/x86_64-linux-gnu/libKF5GuiAddons.so.5
#17 0x7f108def40d4 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffc7a38d290, r=0x560684983020, this=0x560684977590) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#18 doActivate(QObject*, int, void**) (sender=0x560682375de0,
signal_index=3, argv=0x7ffc7a38d290) at kernel/qobject.cpp:3923
#19 0x7f108f8a2e2e in ffi_call_unix64 () at ../src/x86/unix64.S:105
#20 0x7f108f89f493 in ffi_call_int (cif=, fn=, rvalue=, avalue=, closure=)
at ../src/x86/ffi64.c:672
#21 0x7f1090451b20 in  () at /lib/x86_64-linux-gnu/libwayland-client.so.0
#22 0x7f10904522c3 in  () at /lib/x86_64-linux-gnu/libwayland-client.so.0
#23 0x7f10904524bc in wl_display_dispatch_queue_pending () at
/lib/x86_64-linux-gnu/libwayland-client.so.0
#24 0x7f108f92338a in QtWaylandClient::QWaylandDisplay::flushRequests()
(this=) at ./src/client/qwaylanddisplay.cpp:253
#25 0x7f108dee9ade in QObject::event(QEvent*) (this=0x56068235bb50,
e=0x7f107c013b70) at kernel/qobject.cpp:1347
#26 0x7f108ed6c793 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x56068235bb50, e=0x7f107c013b70) at
kernel/qapplication.cpp:3640
#27 0x7f108debc07a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x56068235bb50, event=0x7f107c013b70) at
kernel/qcoreapplication.cpp:1064
#28 0x7f108debf167 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x560682332ec0) at
kernel/qcoreapplication.cpp:1821
#29 0x7f108df16487 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x560682374cc0) at kernel/qeventdispatcher_glib.cpp:277
#30 0x7f108cb5d569 in g_main_dispatch (context=0x7f1084005010) at
../../../glib/gmain.c:3444
#31 g_main_context_dispatch (context=0x7f1084005010) at
../../../glib/gmain.c:4162
#32 0x7f108cbb23c8 in g_main_context_iterate.constprop.0
(context=0x7f1084005010, block=, dispatch=1, self=) at ../../../glib/gmain.c:4238
#33 0x7f108cb5ad20 in g_main_context_iteration (context=0x7f1084005010,
may_block=1) at ../../../glib/gmain.c:4303
#34 0x7f108df15ad8 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x560682387240, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#35 0x7f108deba99b in
QEventL

[plasmashell] [Bug 465326] Plasma crashes when opening kickoff, after freezing for a bit

2023-02-06 Thread Oded Arbel
https://bugs.kde.org/show_bug.cgi?id=465326

Oded Arbel  changed:

   What|Removed |Added

 Resolution|FIXED   |WAITINGFORINFO

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 465326] Plasma crashes when opening kickoff, after freezing for a bit

2023-02-06 Thread Oded Arbel
https://bugs.kde.org/show_bug.cgi?id=465326

Oded Arbel  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED

--- Comment #5 from Oded Arbel  ---
(In reply to Nate Graham from comment #4)
> What kernel version do you have?

I'm still running on 5.19.0.

> It would be very helpful if you could get a backtrace of the hang when it
> happens

The freeze is pretty short, but I'll try - I wrote a script to automate that,
hopefully I can trigger it in time.

What I find interesting is that the crash backtrace shows the crashing thread
is "thread 1", but obviously it wasn't the main thread (it starts with a clone,
i.e. it was created as a thread).

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 465326] Plasma crashes when opening kickoff, after freezing for a bit

2023-02-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=465326

Nate Graham  changed:

   What|Removed |Added

  Component|general |generic-performance
 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO
 CC||n...@kde.org

--- Comment #4 from Nate Graham  ---
What kernel version do you have? With 6.1.7 I was getting a lot of hangs in
statx() system calls. with 6.1.8, it seems to be fixed.

It would be very helpful if you could get a backtrace of the hang when it
happens, if you can either launch Konsole or if it was already running and
didn't hang. You would enter these commands:

$ gdb attach $(pidof plasmashell)
$ bt

And if not, you an do that in a virtual terminal.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 465326] Plasma crashes when opening kickoff, after freezing for a bit

2023-02-05 Thread Oded Arbel
https://bugs.kde.org/show_bug.cgi?id=465326

--- Comment #3 from Oded Arbel  ---
Also, whenever plasmashell crashes, it takes with it some - but not all - of my
running applications: notably, Eclipse, Slack and Google Chrome, but not
Firefox, Konsole or Discover.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 465326] Plasma crashes when opening kickoff, after freezing for a bit

2023-02-05 Thread Oded Arbel
https://bugs.kde.org/show_bug.cgi?id=465326

--- Comment #2 from Oded Arbel  ---
It also happens spontaneously and quite often - it doesn't look to actually
have anything to do with opening the menu, and appear to be related to
activities: plasmashell now freezes when I try to switch activities, either by
using the "next activity" global shortcut, or when trying to open the activity
switcher UI. When it crashes I get the same backtrace (reproduced here):


Thread 1 (Thread 0x7fcbe96ff6c0 (LWP 1256949)):
[KCrash Handler]
#6  __pthread_kill_implementation (no_tid=0, signo=6, threadid=)
at ./nptl/pthread_kill.c:44
#7  __pthread_kill_internal (signo=6, threadid=) at
./nptl/pthread_kill.c:78
#8  __GI___pthread_kill (threadid=, signo=signo@entry=6) at
./nptl/pthread_kill.c:89
#9  0x7fccb4e3bc46 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#10 0x7fccb4e227fc in __GI_abort () at ./stdlib/abort.c:79
#11 0x7fccb52a2b9e in __gnu_cxx::__verbose_terminate_handler() () at
../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95
#12 0x7fccb52ae34c in __cxxabiv1::__terminate(void (*)())
(handler=) at
../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:48
#13 0x7fccb52ae3b7 in std::terminate() () at
../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:58
#14 0x7fccb5690f91 in qTerminate() () at global/qglobal.cpp:3382
#15 0x7fccb5692e3c in QThreadPrivate::start(void*) (arg=0x55f26e7adc80) at
thread/qthread_unix.cpp:342
#16 0x7fccb4e90402 in start_thread (arg=) at
./nptl/pthread_create.c:442
#17 0x7fccb4f1f590 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 465326] Plasma crashes when opening kickoff, after freezing for a bit

2023-02-05 Thread Oded Arbel
https://bugs.kde.org/show_bug.cgi?id=465326

--- Comment #1 from Oded Arbel  ---
Created attachment 155969
  --> https://bugs.kde.org/attachment.cgi?id=155969&action=edit
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

-- 
You are receiving this mail because:
You are watching all bug changes.