Bug 508467 - I closed System Settings whilst a global theme change was applying to Plasma Shell.
Summary: I closed System Settings whilst a global theme change was applying to Plasma ...
Status: RESOLVED DUPLICATE of bug 506642
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (other bugs)
Version First Reported In: 6.4.4
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2025-08-19 12:18 UTC by Roke Julian Lockhart Beedell
Modified: 2025-08-19 12:22 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report: https://crash-reports.kde.org/organizations/kde/issues/234645/events/23cc19789df249c38f6f4a2a1ba0dfbe/


Attachments
New crash information added by DrKonqi (298.41 KB, text/plain)
2025-08-19 12:18 UTC, Roke Julian Lockhart Beedell
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Roke Julian Lockhart Beedell 2025-08-19 12:18:43 UTC
Application: plasmashell (6.4.4)

ApplicationNotResponding [ANR]: false
Qt Version: 6.9.1
Frameworks Version: 6.17.0
Operating System: Linux 6.15.9-201.fc42.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 42 (KDE Plasma Desktop Edition)"
DrKonqi: 6.4.4 [CoredumpBackend]

-- Information about the crash:
This hung it and the shell, for < 2 s. Immediately, the shell closed, then reinvoked, as if I'd executed `kquitapp6 plasmashell && plasmashell`. 

About the warnings at the start of the trace, I've asked https://stackoverflow.com/questions/73812207/gdb-core-dump-warning-cant-open-file-memfdmagicringbuffer-deleted-during-f/73814664#comment140676093_73814664:~:text=If%20you%20think%20you%20can%20file%20such%20a%20bug%2C%20that%20would%20be%20of%20use.%20I%20encounter%20this%20every%20time%20I%20attempt%20to%20debug%20a%20crash%2C%20but%20have%20very%20little%20idea%20of%20any%20of%20the%20concepts%20explained%20here.%20I%20have%20at%20least%20located%20sourceware.org/bugzilla/show_bug.cgi?id=29969. That was all I was able to locate on the topic, so I've been unable to remediate them. Even if I had been able to, this reproduces so rarely/inconsistently that I doubt that I would have been able to generate a new one.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#5  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#6  0x00007f4fe6282163 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:89
#7  0x00007f4fe6228a7e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x00007f4fe62106d0 in __GI_abort () at abort.c:77
#9  0x00007f4fe62116f3 in __libc_message_impl (fmt=fmt@entry=0x7f4fe63c244c "%s\n") at ../sysdeps/posix/libc_fatal.c:134
#10 0x00007f4fe628c1f5 in malloc_printerr (str=str@entry=0x7f4fe63c53b0 "malloc_consolidate(): unaligned fastbin chunk detected") at malloc.c:5829
#11 0x00007f4fe628cecc in malloc_consolidate (av=av@entry=0x7f4fe63f6ac0 <main_arena>) at malloc.c:4903
#12 0x00007f4fe628f930 in _int_malloc (av=0x7f4fe63f6ac0 <main_arena>, bytes=4096) at malloc.c:4099
#13 0x00007f4fe6290dee in __GI___libc_malloc (bytes=4096) at malloc.c:3414
#14 0x00007f4fe6a41f09 in allocateData (allocSize=<optimized out>) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/tools/qarraydata.cpp:139
#15 allocateHelper (objectSize=1, alignment=16, capacity=4078, option=<optimized out>) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/tools/qarraydata.cpp:181
#16 allocateHelper (objectSize=1, alignment=16, capacity=<optimized out>, option=<optimized out>) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/tools/qarraydata.cpp:157
#17 QArrayData::allocate1 (dptr=dptr@entry=0x7fff77fe1890, capacity=<optimized out>, option=<optimized out>) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/tools/qarraydata.cpp:211
#18 0x00007f4fe69cf7e8 in QTypedArrayData<char>::allocate (capacity=<optimized out>, option=<optimized out>) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/tools/qarraydata.h:129
#19 QArrayDataPointer<char>::QArrayDataPointer (this=0x7fff77fe1890, alloc=<optimized out>, n=<optimized out>, option=<optimized out>) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/tools/qarraydatapointer.h:58
#20 QByteArray::reallocData (this=0x7fff77fe1a40, alloc=<optimized out>, option=<optimized out>) at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/text/qbytearray.cpp:1984


Reported using DrKonqi
Comment 1 Roke Julian Lockhart Beedell 2025-08-19 12:18:44 UTC
Created attachment 184250 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Roke Julian Lockhart Beedell 2025-08-19 12:21:40 UTC
(In reply to Roke Julian Lockhart Beedell from comment #0)

In retrospect, this might be a duplicate of https://bugs.kde.org/show_bug.cgi?id=506642#c10. I'll tentatively mark it as so; apologies if not or so. [^1] I should have checked https://bugzilla.redhat.com/show_bug.cgi?id=2376516#c12 first.

[^1]: https://bugzilla.redhat.com/show_bug.cgi?id=2376531#c13

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