From goswin-v-b at web.de  Wed Aug 12 13:32:10 2015
From: goswin-v-b at web.de (Goswin von Brederlow)
Date: Wed, 12 Aug 2015 13:32:10 +0200
Subject: [PySide] Segfault when clicking next in QWizard
Message-ID: <20150812113210.GA25429@frosties>

Hi,

I have a problem with a QWizard in pyside that I can't track down. Every
so often I get a segfault when clicking next or finished ion the wizard:

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000090 in ?? ()
(gdb) bt
#0  0x0000000000000090 in ?? ()
#1  0x00007ffff41dfec3 in ?? ()
   from /usr/lib/python3/dist-packages/PySide/QtGui.cpython-34m-x86_64-linux-gnu.so
#2  0x00007ffff347483b in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#3  0x00007ffff56d087a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) ()
   from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x00007ffff35dd172 in QAbstractButton::clicked(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#5  0x00007ffff3340a63 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#6  0x00007ffff3341bd3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#7  0x00007ffff3341cbc in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#8  0x00007ffff2fde51a in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#9  0x00007ffff2f8ee2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#10 0x00007ffff2f955dd in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#11 0x00007ffff3c6076e in ?? ()
   from /usr/lib/python3/dist-packages/PySide/QtGui.cpython-34m-x86_64-linux-gnu.so
#12 0x00007ffff56bc4dd in QCoreApplication::notifyInternal(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#13 0x00007ffff2f94d93 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#14 0x00007ffff30099eb in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4

I've somewhat reduce the problem to a test case with just the wizard
and uploaded it to github:

    https://github.com/Q-Leap-Networks/pyside-segfault

The segfaults seem to be random. Sometimes they happen, sometimes
everything works. Sometimes the first run through works but when I run
the wizard a second or third time it suddenly segfaults. Sometimes
it's on one of the next buttons and sometimes on finish.

Any help or suggestions how to track this segfault down would be
appreciated.

MfG
	Goswin


From lubos.melichar at gmail.com  Mon Aug 24 11:06:10 2015
From: lubos.melichar at gmail.com (=?UTF-8?Q?Lubo=C5=A1_Melichar?=)
Date: Mon, 24 Aug 2015 11:06:10 +0200
Subject: [PySide] Simple app using a timer to update crahes when
Message-ID: <CAGyA05T4iRzMhDH9bLyo7Zubq-oH6UnPMtBd8iLuBBup+GAkgg@mail.gmail.com>

I have very similar situation.

I am calling


   1. *layoutAboutToBeChanged.emit()*
   2. *than I change the data*
   3. *self.layoutChanged.emit()*

With calling *layoutChanged.emit() *the app crashed.

Did you found any solution?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20150824/5f866dc6/attachment.html>