On Wed, Aug 12, 2015 at 08:29:28PM +0200, Didier 'OdyX' Raboud wrote:
Le mercredi, 12 août 2015, 16.00:22 Goswin von Brederlow a écrit :
Le jeudi, 6 août 2015, 14.40:10 Goswin von Brederlow a écrit :
every now and then pyside crashes with a segfault. Most often
because
it doesn't
On Thu, Aug 06, 2015 at 05:51:59PM +0200, Didier 'OdyX' Raboud wrote:
Control: found -1 1.0.9-2
Le jeudi, 6 août 2015, 14.40:10 Goswin von Brederlow a écrit :
every now and then pyside crashes with a segfault. Most often because
it doesn't play nice with the python GC and widgets have to
On Thu, Aug 06, 2015 at 05:51:59PM +0200, Didier 'OdyX' Raboud wrote:
Control: found -1 1.0.9-2
Le jeudi, 6 août 2015, 14.40:10 Goswin von Brederlow a écrit :
every now and then pyside crashes with a segfault. Most often because
it doesn't play nice with the python GC and widgets have to
Le mercredi, 12 août 2015, 16.00:22 Goswin von Brederlow a écrit :
Le jeudi, 6 août 2015, 14.40:10 Goswin von Brederlow a écrit :
every now and then pyside crashes with a segfault. Most often
because
it doesn't play nice with the python GC and widgets have to keep
python objects
Source: pyside
Severity: important
Hi,
every now and then pyside crashes with a segfault. Most often because
it doesn't play nice with the python GC and widgets have to keep
python objects stored in C++ alive manually. But sometimes it isn't
obvious where and why pyside segfaults. For those it
Control: found -1 1.0.9-2
Le jeudi, 6 août 2015, 14.40:10 Goswin von Brederlow a écrit :
every now and then pyside crashes with a segfault. Most often because
it doesn't play nice with the python GC and widgets have to keep
python objects stored in C++ alive manually. But sometimes it isn't
6 matches
Mail list logo
