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

--- Comment #3 from Matt Fagnani <matthew.fagn...@utoronto.ca> ---
Created attachment 121409
  --> https://bugs.kde.org/attachment.cgi?id=121409&action=edit
coredumpctl gdb output of segmentation fault in powerdevil when logging of
Plasma on Wayland

Thanks Christoph. I think that if the segmentation faults in powerdevil were
fixed then the aborts of drkonqi and the restarted powerdevil after the Wayland
compositor connection was broken wouldn't happen. I saw another segmentation
fault in powerdevil when I logged out of Plasma 5.15.5 on Wayland. sddm didn't
show up and the screen stayed blank which I've seen many times before when
logging out of Plasma on Wayland. I pressed sysrq+alt+e , sysrq+alt+i which
terminated then killed most of the userspace processes. sddm restarted after
that.

This segmentation fault occurred at about the same time that the screen went
blank. coredumpctl gdb showed that  tc_victim->fd in _int_malloc at
malloc.c:3623 was an inaccessible address.
Core was generated by `/usr/libexec/org_kde_powerdevil'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f0d44dcadac in _int_malloc (av=av@entry=0x7f0d2c000020,
bytes=bytes@entry=65)
    at malloc.c:3622
3622                          if (SINGLE_THREAD_P)
[Current thread is 1 (Thread 0x7f0d33b86700 (LWP 1559))]

(gdb) list
3617
3618                      /* While bin not empty and tcache not full, copy
chunks.  */
3619                      while (tcache->counts[tc_idx] < mp_.tcache_count
3620                             && (tc_victim = *fb) != NULL)
3621                        {
3622                          if (SINGLE_THREAD_P)
3623                            *fb = tc_victim->fd;
3624                          else
3625                            {
3626                              REMOVE_FB (fb, pp, tc_victim);

(gdb) p tc_victim->fd
Cannot access memory at address 0xa10000556b
(gdb) p tc_victim
$2 = (mchunkptr) 0xa10000555b

A signal indicating a crash appeared after #13 in tcache_get at malloc.c:2952.
KCrash::defaultCrashHandler in #11 showed errors like "Cannot access memory at
address 0x7" which might indicate memory corruption. Qt string conversions
involving "org.kde.kglobalaccel" happened at #16-19. I've seen many aborts of
kglobalaccel5 when logging out of Plasma on Wayland and X as reported at
https://bugzilla.redhat.com/show_bug.cgi?id=1701485

I've attached the coredumpctl gdb output of the crash with the full backtrace
of all threads etc. I reported this crash in more detail at
https://bugzilla.redhat.com/show_bug.cgi?id=1727470  Should I create a new
report on bugs.kde.org since the trace is different?

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

Reply via email to