segfault on application exit

[Kevin Turner]

pylotro segfaults on exit. seemingly on every exit, even if I just start the app and exit again without launching or patching anything.

Exit is not a terrible time to segfault, but it makes me worry if whatever is causing this may be behind other problems.

using python 2.6 on Ubuntu Lucid Lynx beta, 64-bit.
---
Architecture: amd64
DistroRelease: Ubuntu 10.04
NonfreeKernelModules: nvidia
Package: pylotro 0.1.11lucid0 [modified: usr/bin/pylotro]
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.utf8
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Tags: lucid
Uname: Linux 2.6.32-19-generic x86_64
UnreportableReason: This is not a genuine Ubuntu package
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev pulse-access sambashare scanner vboxusers video

[Kevin Turner (keturn)]

the gdb crash I reference at the end is ubuntu bug #544597

[Kevin Turner (keturn)]

apport information

[Alan Jackson (ajackson-bcs)]

It looks to be a problem with deallocating memory once the application has finished, so the only thing it is affecting is the smooth close of the application.

Since it is only happening on Lucid and the program code hasn't altered I'm going to monitor it to see if it is just a new problem with QT4 and/or PyQt4 (QT4 was updated on 7th April so it could be a regression in that).

[Umang Varma (umang)]

I'm making a pretty wild guess here, but I believe it is a problem in PyQt. I was trying my own project (pynagram) on Windows with 4.7.2 and I'd get a crash on exit. Similarly, my project hasn't changed since I was on Karmic and I never encountered this problem. I do now on Lucid. When I tried to use it with 4.7.3 on Windows, there was no crash on exit. If this can be tested with 4.7.3 on Lucid, then there would be a case for pyqt4 to be upgraded in the repos.

[Alan Jackson (ajackson-bcs)]

There is a bug report for this problem that agrees that the cause is PyQt4 4.7.2.

See https://bugs.launchpad.net/pylotro/+bug/561303