X-Received: by 10.140.165.203 with SMTP id l194mr18502487qhl.4.1434697292747; Fri, 19 Jun 2015 00:01:32 -0700 (PDT)
X-Received: by 10.140.21.197 with SMTP id 63mr278370qgl.31.1434697292723; Fri, 19 Jun 2015 00:01:32 -0700 (PDT)
Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!peer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!q107no2055539qgd.0!news-out.google.com!k20ni2665qgd.0!nntp.google.com!z60no2053948qgd.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.python
Date: Fri, 19 Jun 2015 00:01:32 -0700 (PDT)
In-Reply-To: <mailman.216.1433590803.13271.python-list@python.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=195.33.129.54; posting-account=ZwMl3QoAAAABQuDxpiwn1RyKb0YaHXCC
NNTP-Posting-Host: 195.33.129.54
References: <8a6ed08d-7dd6-4a4a-a466-9d3ad98f8dff@googlegroups.com> <c5370bc0-00ee-49be-9ecd-2e25008a78c5@googlegroups.com><mkrp99$b6d$1@dont-email.me> <mailman.216.1433590803.13271.python-list@python.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <ea13e85b-bb82-4cb2-99d7-5296ebce733c@googlegroups.com>
Subject: [Solved] Python.exe has stopped working
From: Alexis Dubois <alex@duboaa.net>
Injection-Date: Fri, 19 Jun 2015 07:01:32 +0000
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 2894
X-Received-Body-CRC: 3471192451
Xref: csiph.com comp.lang.python:92872

Le samedi 6 juin 2015 13:40:13 UTC+2, Laura Creighton a =E9crit=A0:
> In a message of Fri, 05 Jun 2015 11:15:31 +0200, Christian Gollwitzer wri=
tes:
> >Am 05.06.15 um 11:03 schrieb Alexis Dubois:
> >> Anyone else for an idea on that?
> >>
> >Well, it is a crash on exit. Looks like a memory error inside of PyQT.=
=20
> >If you've got the time, you could run it inside of a debugger, or=20
> >better, a memory checker like AppVerifier to find the culprit. These=20
> >things are usually quite hard to diagnose, and unless someone has seen=
=20
> >it here already, the fun starts now ;) Another possible reason might be=
=20
> >mixing up DLLs from PyQT and another QT installation. You can find out=
=20
> >by listing all loaded DLLs when the program is running, e.g. from a=20
> >debugger or this tool:=20
> >https://technet.microsoft.com/sysinternals/bb896653.aspx
> >
> >	Christian
> >--=20
> >https://mail.python.org/mailman/listinfo/python-list
>=20
> I don't have a windows machine, so I cannot do any more looking for this,
> but this may be relevant.
> http://stackoverflow.com/questions/20102419/pyqt-5-error-on-exit
>=20
> Laura

Hello Everybody,
Thank you for your support and sorry for the late answer, I'm back from hol=
idays.
I tried each solution but unfortunately, nothing works.
Finally, I solved my issue by adding "sip.setdestroyonexit(False)" just bef=
ore "sys.exit(app.exec_())"
I don't really know what it does but it works well and I don't see any besi=
de effect.
It seems that my issue was linked with a QtGui4.dll crash.