Description of problem:
I was using Firefox 122.0a1 (2023-12-01) on Wayland in Plasma 5.27.9 in a Fedora 39 KDE Plasma installation. I logged into my Instagram account in Firefox. I played various Instagram stories. As one Instagram story video ended and another began, plasmashell crashed. drkonqi appeared for reporting the plasmashell crash. I pressed Developer Information in drkonqi. drkonqi crashed while it was creating a trace. Another drkonqi window appeared for the drkonqi trace. I pressed Developer Information again in drkonqi. drkonqi crashed again. An abrt notification was shown. A gdb crash was shown in abrt and coredumpctl.

This gdb crash was during the plasmashell crash trace in drkonqi. I reported a gdb crash which happened in a similar way at https://bugzilla.redhat.com/show_bug.cgi?id=2252382 That trace looked different from this one so I'm reporting it separately. Since the plasmashell crashes when watching videos in Firefox were infrequent as I reported at https://bugzilla.redhat.com/show_bug.cgi?id=2216067 and https://bugzilla.redhat.com/show_bug.cgi?id=2250389 I found a way to reproduce the plasmashell crash and gdb crash in drkonqi such that plasmashell will crash every time at least. I reported those steps at https://bugzilla.redhat.com/show_bug.cgi?id=2252382#c11 

Version-Release number of selected component:
gdb-headless-13.2-11.fc39

Additional info:
reporter:       libreport-2.17.11
cmdline:        /usr/bin/gdb -nw -n -batch -x /tmp/drkonqi.cwGjyw -x /tmp/drkonqi.uZPVDQ -p 58309 /usr/bin/plasmashell
rootdir:        /
executable:     /usr/libexec/gdb
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/plasma-plasmashell.service
type:           CCpp
kernel:         6.6.3-200.fc39.x86_64
runlevel:       N 5
journald_cursor: s=835a8447cd6d443b95149316ea1b512b;i=11efe3b;b=6104c25cf4454599b8d5b06175cb508f;m=586073d29;t=60b7d1d8bf4ff;x=b6c688b51e46d440
package:        gdb-headless-13.2-11.fc39
backtrace_rating: 4
uid:            1000
crash_function: handle_fatal_signal
reason:         gdb killed by SIGABRT

Truncated backtrace:
Thread no. 0 (12 frames)
 #3 handle_fatal_signal at ../../gdb/event-top.c:985
 #5 __futex_abstimed_wait_common64 at futex-internal.c:57
 #6 __futex_abstimed_wait_common at futex-internal.c:87
 #7 __futex_abstimed_wait_cancelable64 at futex-internal.c:139
 #8 __pthread_cond_wait_common at pthread_cond_wait.c:503
 #9 ___pthread_cond_wait at pthread_cond_wait.c:618
 #10 __gthread_cond_wait at /usr/src/debug/gcc-13.2.1-4.fc39.x86_64/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/x86_64-redhat-linux/bits/gthr-default.h:865
 #11 std::__condvar::wait at /usr/src/debug/gcc-13.2.1-4.fc39.x86_64/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/std_mutex.h:171
 #12 std::condition_variable::wait at ../../../../../libstdc++-v3/src/c++11/condition_variable.cc:41
 #13 gdb::thread_pool::thread_function at ../../gdbsupport/thread-pool.cc:235
 #14 std::execute_native_thread_routine at ../../../../../libstdc++-v3/src/c++11/thread.cc:104
 #16 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78


Potential duplicate: bug 2242572