Bug 416033 - Kwin crash with kwin-tiling enabled when launching a VM
Summary: Kwin crash with kwin-tiling enabled when launching a VM
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.17.5
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2020-01-09 07:58 UTC by damien.mourey
Modified: 2022-11-05 05:09 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
journalctl output (6.20 KB, text/plain)
2020-01-16 13:50 UTC, damien.mourey
Details
New crash information added by DrKonqi (4.20 KB, text/plain)
2020-10-03 18:23 UTC, Guillem Larrosa Jara
Details

Note You need to log in before you can comment on or make changes to this bug.
Description damien.mourey 2020-01-09 07:58:17 UTC
Application: kwin_x11 (5.17.5)

Qt Version: 5.14.0
Frameworks Version: 5.65.0
Operating System: Linux 5.4.8-arch1-1 x86_64
Distribution: Arch Linux

-- Information about the crash:
- What I was doing when the application crashed:

Started a Windows 10 virtual machine in virtual box, while the kwin-tiling script was enabled. I don't recall of it happening with the script disabled.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb3495c8880 (LWP 213902))]

Thread 5 (Thread 0x7fb342dee700 (LWP 214386)):
#0  0x00007fb34ee0ac45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0
#1  0x00007fb34fc6acc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5
#2  0x00007fb34fc6ada2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5
#3  0x00007fb34e8bd18b in  () at /usr/lib/libQt5Quick.so.5
#4  0x00007fb34e8bd41b in  () at /usr/lib/libQt5Quick.so.5
#5  0x00007fb34fc64fd6 in  () at /usr/lib/libQt5Core.so.5
#6  0x00007fb34ee044cf in start_thread () at /usr/lib/libpthread.so.0
#7  0x00007fb3514502d3 in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7fb340ee6700 (LWP 213921)):
#0  0x00007fb34ee0ac45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0
#1  0x00007fb34f75ef3c in  () at /usr/lib/libQt5Script.so.5
#2  0x00007fb34f75ef59 in  () at /usr/lib/libQt5Script.so.5
#3  0x00007fb34ee044cf in start_thread () at /usr/lib/libpthread.so.0
#4  0x00007fb3514502d3 in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7fb342127700 (LWP 213911)):
#0  0x00007fb351445ae6 in ppoll () at /usr/lib/libc.so.6
#1  0x00007fb34fe93cc3 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5
#2  0x00007fb34fe952dd in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#3  0x00007fb34fe3e39c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#4  0x00007fb34fc63e62 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x00007fb34e523249 in  () at /usr/lib/libQt5Qml.so.5
#6  0x00007fb34fc64fd6 in  () at /usr/lib/libQt5Core.so.5
#7  0x00007fb34ee044cf in start_thread () at /usr/lib/libpthread.so.0
#8  0x00007fb3514502d3 in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7fb343fff700 (LWP 213906)):
#0  0x00007fb351445ae6 in ppoll () at /usr/lib/libc.so.6
#1  0x00007fb34fe93cc3 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5
#2  0x00007fb34fe952dd in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#3  0x00007fb34fe3e39c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#4  0x00007fb34fc63e62 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x00007fb34dea2b28 in  () at /usr/lib/libQt5DBus.so.5
#6  0x00007fb34fc64fd6 in  () at /usr/lib/libQt5Core.so.5
#7  0x00007fb34ee044cf in start_thread () at /usr/lib/libpthread.so.0
#8  0x00007fb3514502d3 in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7fb3495c8880 (LWP 213902)):
[KCrash Handler]
#6  0x00007fb34e29260c in  () at /usr/lib/libQt5Qml.so.5
#7  0x00007fb34e318cea in QV4::PersistentValueStorage::mark(QV4::MarkStack*) () at /usr/lib/libQt5Qml.so.5
#8  0x00007fb34e29298e in QV4::MemoryManager::collectRoots(QV4::MarkStack*) () at /usr/lib/libQt5Qml.so.5
#9  0x00007fb34e292b7e in QV4::MemoryManager::mark() () at /usr/lib/libQt5Qml.so.5
#10 0x00007fb34e294672 in  () at /usr/lib/libQt5Qml.so.5
#11 0x00007fb34e296aaa in QV4::MemoryManager::allocData(unsigned long) () at /usr/lib/libQt5Qml.so.5
#12 0x00007fb34e320f0f in QV4::ArrayData::realloc(QV4::Object*, QV4::Heap::ArrayData::Type, unsigned int, bool) () at /usr/lib/libQt5Qml.so.5
#13 0x00007fb34e328dbe in  () at /usr/lib/libQt5Qml.so.5
#14 0x00007fb34e3c7bf5 in QV4::Runtime::CallProperty::call(QV4::ExecutionEngine*, QV4::Value const&, int, QV4::Value*, int) () at /usr/lib/libQt5Qml.so.5
#15 0x00007fb325391258 in  ()
#16 0x0000000000000000 in  ()
[Inferior 1 (process 213902) detached]

Possible duplicates by query: bug 415991, bug 415960, bug 415956, bug 415930, bug 415824.

Reported using DrKonqi
Comment 1 Vlad Zahorodnii 2020-01-16 13:42:10 UTC
Hmm, looks like something fishy is going on when qtquick performs garbage collection. Were you able to reproduce this crash with older versions of Qt?
Comment 2 David Edmundson 2020-01-16 13:47:57 UTC
Please can you confirm which script and at which version.

Is the crash reproducible every time?
Comment 3 damien.mourey 2020-01-16 13:50:25 UTC
Created attachment 125170 [details]
journalctl output
Comment 4 damien.mourey 2020-01-16 13:53:00 UTC
Comment on attachment 125170 [details]
journalctl output

This is the output of journalctl.
The bug is easy to reproduce, it happens when resizing windows. Not always, but very often, 1 time out of 4 on average.
Comment 5 damien.mourey 2020-01-16 13:56:26 UTC
(In reply to David Edmundson from comment #2)
> Please can you confirm which script and at which version.
> 
> Is the crash reproducible every time?

I use the following kwin-tiling script in version 2.3 : https://github.com/kwin-scripts/kwin-tiling/releases/tag/v2.3

The bug is reproducible by resizing windows.
Comment 6 Bug Janitor Service 2020-01-31 04:33:15 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Christoph Feck 2020-02-04 00:25:42 UTC
Requested information was added with comment 5; changing status for inspection.
Comment 8 Guillem Larrosa Jara 2020-10-03 18:23:06 UTC
Created attachment 132099 [details]
New crash information added by DrKonqi

kwin_x11 (5.19.5) using Qt 5.15.0

- What I was doing when the application crashed:
I opened Kate from the terminal, and when the kwin-tiling-script extension resized the terminal that was using all the screen for giving half to Kate, Kwin cashed.

- Custom settings of the application:
kwin-tiling

-- Backtrace (Reduced):
#4  0x00007f929cba8db4 in QV4::MarkStack::drain() (this=this@entry=0x7ffd02dd0b40) at ../../include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/memory/qv4heap_p.h:73
#5  0x00007f929cba96a9 in QV4::MarkStack::~MarkStack() (this=0x7ffd02dd0b40, __in_chrg=<optimized out>) at ../../include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/memory/qv4mmdefs_p.h:276
#6  QV4::MemoryManager::mark() (this=this@entry=0x564448d16560) at memory/qv4mm.cpp:915
#7  0x00007f929cbab1c6 in QV4::MemoryManager::runGC() (this=0x564448d16560) at memory/qv4mm.cpp:1050
#8  0x00007f929cbad498 in QV4::MemoryManager::allocate(QV4::BlockAllocator*, unsigned long) (size=128, allocator=0x564448d16570, this=0x564448d16560) at ../../include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/memory/qv4mm_p.h:328
Comment 9 Justin Zobel 2022-10-06 06:36:30 UTC
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 10 Bug Janitor Service 2022-10-21 05:00:54 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 11 Bug Janitor Service 2022-11-05 05:09:18 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!