Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tk.quit and sys.exit cause Fatal Error #39515

Closed
blaforge mannequin opened this issue Nov 6, 2003 · 7 comments
Closed

Tk.quit and sys.exit cause Fatal Error #39515

blaforge mannequin opened this issue Nov 6, 2003 · 7 comments
Assignees

Comments

@blaforge
Copy link
Mannequin

blaforge mannequin commented Nov 6, 2003

BPO 837234
Nosy @loewis, @mkiever
Superseder
  • bpo-775544: Tk.quit leads to crash in python.exe
  • Files
  • issue837234.py: Failed to reproduce the bug
  • issue775544.py: demo code from issue 775544 (does not reproduce bug on linux)
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = 'https://github.com/loewis'
    closed_at = <Date 2008-06-01.11:30:06.140>
    created_at = <Date 2003-11-06.15:05:34.000>
    labels = ['expert-tkinter']
    title = 'Tk.quit and sys.exit cause Fatal Error'
    updated_at = <Date 2008-06-01.11:30:06.139>
    user = 'https://bugs.python.org/blaforge'

    bugs.python.org fields:

    activity = <Date 2008-06-01.11:30:06.139>
    actor = 'georg.brandl'
    assignee = 'loewis'
    closed = True
    closed_date = <Date 2008-06-01.11:30:06.140>
    closer = 'georg.brandl'
    components = ['Tkinter']
    creation = <Date 2003-11-06.15:05:34.000>
    creator = 'blaforge'
    dependencies = []
    files = ['10242', '10356']
    hgrepos = []
    issue_num = 837234
    keywords = []
    message_count = 7.0
    messages = ['18921', '18922', '55383', '55413', '55415', '66521', '67005']
    nosy_count = 5.0
    nosy_names = ['loewis', 'jafo', 'blaforge', 'mkiever', 'werneck']
    pr_nums = []
    priority = 'high'
    resolution = 'duplicate'
    stage = None
    status = 'closed'
    superseder = '775544'
    type = None
    url = 'https://bugs.python.org/issue837234'
    versions = []

    @blaforge
    Copy link
    Mannequin Author

    blaforge mannequin commented Nov 6, 2003

    Fatal Python error: PyEval_RestoreThread: NULL tstate

    I get this if I do a sys.exit() or a Tkinter quit() from with
    an after call or from capturing an input event.

    HOWEVER, if I capture a <Destroy> event and then call
    quit(), everything works fine!

    @blaforge blaforge mannequin assigned loewis Nov 6, 2003
    @blaforge blaforge mannequin added the topic-tkinter label Nov 6, 2003
    @blaforge blaforge mannequin assigned loewis Nov 6, 2003
    @blaforge blaforge mannequin added the topic-tkinter label Nov 6, 2003
    @blaforge
    Copy link
    Mannequin Author

    blaforge mannequin commented Nov 6, 2003

    Logged In: YES
    user_id=22406

    Ah! Calling destroy works.

    @jafo
    Copy link
    Mannequin

    jafo mannequin commented Aug 28, 2007

    Is this a bug or just incorrect usage? From reading the message it
    sounds like it may just have been an incorrect usage.

    If it's a bug, can we get a sample that reproduces the problem?

    @loewis
    Copy link
    Mannequin

    loewis mannequin commented Aug 29, 2007

    It should not be possible to trigger Py_FatalError through pure Python
    code. I still haven't tried reproducing the problem, but if it is
    reproducable, it's a bug.

    @jafo
    Copy link
    Mannequin

    jafo mannequin commented Aug 29, 2007

    blaforge: I know it's been years, but can you provide code that
    reproduces this? I'm going to switch it to "pending" state, please
    re-open when you include some code to reproduce it.

    @werneck
    Copy link
    Mannequin

    werneck mannequin commented May 10, 2008

    I tried reproducing the bug with the info provided but neither case
    worked. Since it doesn't mention platform, I'm including the file in
    case anyone wants to try it on anything other than Linux/Python2.5.

    @mkiever
    Copy link
    Mannequin

    mkiever mannequin commented May 17, 2008

    Hi,

    found a related (duplicate ?) issue
    which mentions a platform and has code
    producing the error:
    http://bugs.python.org/issue775544
    Can someone based on WinXP try the code?
    Attaching it here for easier reference.
    Works without problem on my Linux 2.6,
    Python 2.4.1 with Tk 8.4

    Guess the other issue is similar enough
    to close it.

    Regards,
    Matthias Kievernagel

    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 9, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Projects
    None yet
    Development

    No branches or pull requests

    1 participant