https://bugs.kde.org/show_bug.cgi?id=506642

            Bug ID: 506642
           Summary: "plasma-workspace: allocateData(): plasmashell killed
                    by SIGABRT" when an erroneous modal appeared switching
                    global themes from Quick Settings
    Classification: Plasma
           Product: plasmashell
      Version First 6.4.1
       Reported In:
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: generic-crash
          Assignee: plasma-b...@kde.org
          Reporter: 4wy78...@rokejulianlockhart.addy.io
  Target Milestone: 1.0

Application: plasmashell (6.4.1)

ApplicationNotResponding [ANR]: false
Qt Version: 6.9.1
Frameworks Version: 6.15.0
Operating System: Linux 6.15.4-200.fc42.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 42 (KDE Plasma Desktop Edition)"
DrKonqi: 6.4.1 [CoredumpBackend]

-- Information about the crash:
Per https://bugzilla.redhat.com/show_bug.cgi?id=2376516, at the "Quick
Settings" page, [^1] I attempted to switch global theme from
`org.kde.breezedark.desktop` to `org.kde.breeze.desktop` (like `lookandfeel
--apply` would). Although I *believe* that I hit "Apply", after which the theme
changed, *then* the window decoration's closure button. When I did, "Apply
Settings" modal window appeared regardless. When I selected "Apply", the window
closed, and the theme reverted, for the applications, but didn't for the shell.
After 0.75s, the shell crashed and automatically reloaded, whereupon Dr Konqi
and GNOME Abrt invoked.

[^1]:
https://discuss.kde.org/t/which-kcm-maps-to-quick-settings-does-one/36650?u=rokejulianlockhart

The crash does not seem to be reproducible.

-- 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  0x00007fa6566811e3 in __pthread_kill_internal (threadid=<optimized out>,
signo=6) at pthread_kill.c:89
#7  0x00007fa656627afe in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#8  0x00007fa65660f6d0 in __GI_abort () at abort.c:73
#9  0x00007fa6566106f3 in __libc_message_impl (fmt=fmt@entry=0x7fa6567c248c
"%s\n") at ../sysdeps/posix/libc_fatal.c:134
#10 0x00007fa65668b275 in malloc_printerr (str=str@entry=0x7fa6567c5498
"malloc_consolidate(): unaligned fastbin chunk detected") at malloc.c:5829
#11 0x00007fa65668bf4c in malloc_consolidate (av=av@entry=0x7fa6567f6ac0
<main_arena>) at malloc.c:4903
#12 0x00007fa65668e9b0 in _int_malloc (av=0x7fa6567f6ac0 <main_arena>,
bytes=4096) at malloc.c:4099
#13 0x00007fa65668fe6e in __GI___libc_malloc (bytes=4096) at malloc.c:3414
#14 0x00007fa656e41f09 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=0x7ffca39fc6c0, 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 0x00007fa656dcf7e8 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=0x7ffca39fc6c0,
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=0x7ffca39fc870, 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

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

Reply via email to