[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    [PyQt] PyQt5 segfault on exit
From:       pwuertz <pwuertz () gmail ! com>
Date:       2014-09-08 17:35:31
Message-ID: 1410197731405-5070867.post () n6 ! nabble ! com
[Download RAW message or body]

I also get segmentation faults in about 1 out of 10 runs when closing a PyQt5
application on multiple machines/systems (Ubuntu 14.04 and 14.10) and
configurations (python2 and python3, pyqt5 from distribution and self
compiled). The test application is a single QQuickView window with a
Rectangle as root object.

Although I ran python3-dbg within gdb I don't seem to get any useful
information from the bt, but "info threads" points at QXcbEventReader, as
reported by Roger Leigh:
(gdb) info threads
  Id   Target Id         Frame 
  6    Thread 0x7fffd632d700 (LWP 3651) "QSGRenderThread"
pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  5    Thread 0x7fffd7dff700 (LWP 3650) "QThread" 0x00007ffff6b8bc6d in poll
()
    at ../sysdeps/unix/syscall-template.S:81
  4    Thread 0x7fffdce57700 (LWP 3649) "gdbus" 0x00007ffff6b8bc6d in poll
()
    at ../sysdeps/unix/syscall-template.S:81
  3    Thread 0x7fffdd86a700 (LWP 3648) "dconf worker" 0x00007ffff6b8bc6d in
poll () at ../sysdeps/unix/syscall-template.S:81
* 2    Thread 0x7fffe8ea9700 (LWP 3647) "QXcbEventReader" 0x00007fffec0d2729
in ?? ()
  1    Thread 0x7ffff7fd0740 (LWP 3643) "python3-dbg" 0x00007fffeff45340 in
??
    () from /usr/lib/nvidia-331/libnvidia-glcore.so.331.38




--
View this message in context: \
http://python.6.x6.nabble.com/PyQt5-segfault-when-closing-a-QMainWindow-tp5026465p5070867.html \
Sent from the PyQt mailing list archive at Nabble.com. \
_______________________________________________ PyQt mailing list    \
PyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt


[prev in list] [next in list] [prev in thread] [next in thread]