This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Python 3.6.0
Type: crash Stage: resolved
Components: Interpreter Core Versions: Python 3.6
process
Status: closed Resolution: third party
Dependencies: Superseder:
Assigned To: Nosy List: PedanticHacker, lazka, r.david.murray
Priority: normal Keywords:

Created on 2017-02-25 10:44 by PedanticHacker, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (3)
msg288557 - (view) Author: Boštjan Mejak (PedanticHacker) * Date: 2017-02-25 10:44
I managed to create an app that crashes the latest stable version of Python, that is 3.6.0 at the time of this writing.

My application is written in Python using wxPython Phoenix 3rd-party GUI library/toolkit. I am running Windows 10 Home 64-bit version OS, the latest version of it, the Anniversary Edition with all its updates.

How I did it? Well, I made an event in my GUI app where clicking the X button puts up a message dialog to the user, saying "Do you really wanna close this app?" and the "Yes" button destroys the whole object, thus exiting the application.

But now the catch! I also made a taskbar icon which includes a menu item to also exit the application: same message dialog with Yes/No buttons.

Let's crash this baby! If you click the X button and not choosing either "Yes" or "No" but instead have this message dialog wait and in the mean time you right-click the taskbar icon and choose the "Exit" menu item and choose "Yes". Then click another "Yes" of that waiting message dialog and BOOM! Voila, we have killed PYthon interpreter.

Is that a bug in my code or does Python have a weakness?
msg288559 - (view) Author: Christoph Reiter (lazka) * Date: 2017-02-25 11:14
That sounds like a problem with wxPython which you should report to them: http://trac.wxwidgets.org/

When you do, try to attach a minimal code example with your instructions so others can reproduce the error.
msg288573 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2017-02-25 17:53
Agreed with Christoph.  If the wxPython team finds there really is a bug in cpython itself triggering this, they (or you) can open a new issue with specifics.
History
Date User Action Args
2022-04-11 14:58:43adminsetgithub: 73833
2017-02-25 18:25:00gvanrossumsetnosy: - gvanrossum
2017-02-25 17:53:11r.david.murraysetstatus: open -> closed

nosy: + r.david.murray
messages: + msg288573

resolution: third party
stage: resolved
2017-02-25 11:14:44lazkasetnosy: + lazka
messages: + msg288559
2017-02-25 10:44:46PedanticHackercreate