Bug 433791 - Crash when closing window after being opened more than once
Summary: Crash when closing window after being opened more than once
Status: REPORTED
Alias: None
Product: kwayland
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.79.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Martin Flöser
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-01 13:40 UTC by kde
Modified: 2021-03-08 12:20 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
kinfocenter backtrace (17.92 KB, text/vnd.kde.kcrash-report)
2021-03-01 16:15 UTC, kde
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kde 2021-03-01 13:40:24 UTC
SUMMARY
KInfoCenter crashes when closing it after having started it multiple times.

STEPS TO REPRODUCE
1. Open KInfoCenter
2. Open KInfoCenter again, without closing the first instance
3. There's still just one instance running, probably intentional
4. Close KInfoCenter

OBSERVED RESULT
Crash

EXPECTED RESULT
Clean exit

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20210223
KDE Plasma Version: 5.21.0
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.10.16-1-default
OS Type: 64-bit
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: Radeon RX 570 Series
Comment 1 Alois Wohlschlager 2021-03-01 15:40:20 UTC
Please supply a backtrace of the crash.
Comment 2 kde 2021-03-01 16:15:09 UTC
Created attachment 136284 [details]
kinfocenter backtrace
Comment 3 Nate Graham 2021-03-02 16:28:18 UTC
[KCrash Handler]
#4  0x00007f505a2c6495 in raise () from /lib64/libc.so.6
#5  0x00007f505a2af864 in abort () from /lib64/libc.so.6
#6  0x00007f505a72e0e7 in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914
#7  QMessageLogger::fatal (this=this@entry=0x7f4f9193fa10, msg=msg@entry=0x7f505b32c7f8 "QPixmap: Must construct a QGuiApplication before a QPixmap") at global/qlogging.cpp:893
#8  0x00007f505ae5260d in qt_pixmap_thread_test () at image/qpixmap.cpp:76
#9  qt_pixmap_thread_test () at image/qpixmap.cpp:73
#10 0x00007f505af27da5 in QPixmap::QPixmap (this=0x7f4f9193fa90) at image/qpixmap.cpp:111
#11 0x00007f505af3633e in QPixmapIconEngine::read (this=0x7f4f88012750, in=...) at image/qicon.cpp:483
#12 0x00007f505af39cc6 in operator>> (s=..., icon=...) at image/qicon.cpp:1453
#13 0x00007f50558eff8a in ?? () from /usr/lib64/libKF5WaylandClient.so.5
#14 0x00007f505a76c1f2 in QThreadPoolThread::run (this=0x55e2f5cbc890) at thread/qthreadpool.cpp:100
#15 0x00007f505a768ef1 in QThreadPrivate::start (arg=0x55e2f5cbc890) at thread/qthread_unix.cpp:329
#16 0x00007f5058f21299 in start_thread () from /lib64/libpthread.so.0
#17 0x00007f505a389af3 in clone () from /lib64/libc.so.6


Cannot reproduce the crash with those instructions.
Comment 4 Harald Sitter 2021-03-08 12:20:23 UTC
Crash is in kwayland. Moving bug.

The backtrace is unfortunately missing the most important frame.