[issue34927] Tkinter-related segfault on macOS (regression between 3.7.0 and 3.7.1rc1)

Karthikeyan Singaravelan added the comment: Thanks for the release Ned. I can confirm that there is no segfault with Python 3.7.1rc2 (v3.7.1rc2:6c06ef7dc3). -- ___ Python tracker ___

[issue34927] Tkinter-related segfault on macOS (regression between 3.7.0 and 3.7.1rc1)

Ned Deily added the comment: It appears that the segfault behavior *was* introduced by some change in the Tk 8.6 development snapshot I chose to use for the python.org macOS installer builds in 3.7.1rc1 and 3.6.7rc2. For 3.7.1rc2 and 3.6.7rc2, I reverted back to using the standard Tk 8.6.8

[issue34927] Tkinter-related segfault on macOS (regression between 3.7.0 and 3.7.1rc1)

Ned Deily added the comment: New changeset d8b6425e58a1fccdf8ddbbcde63066c13c1bcfaf by Ned Deily in branch '3.7': bpo-34370: Revert to using released Tk 8.6.8 with macOS installers https://github.com/python/cpython/commit/d8b6425e58a1fccdf8ddbbcde63066c13c1bcfaf --

[issue34927] Tkinter-related segfault on macOS (regression between 3.7.0 and 3.7.1rc1)

Ned Deily added the comment: New changeset f55c3ae657595d12ce78aca76c9c6b998d632424 by Ned Deily in branch '3.6': bpo-34370: Revert to using released Tk 8.6.8 with macOS installers https://github.com/python/cpython/commit/f55c3ae657595d12ce78aca76c9c6b998d632424 --

[issue34927] Tkinter-related segfault on macOS (regression between 3.7.0 and 3.7.1rc1)

Ned Deily added the comment: > Can it be caused by > https://github.com/python/cpython/commit/adf493227f1efd5d6b34f46b854142bf3b5a411c > ? It very likely could be. Thanks for the report. I'll take a look at it a bit later. -- assignee: -> ned.deily _

[issue34927] Tkinter-related segfault on macOS (regression between 3.7.0 and 3.7.1rc1)

Aivar Annamaa added the comment: Can it be caused by https://github.com/python/cpython/commit/adf493227f1efd5d6b34f46b854142bf3b5a411c ? -- ___ Python tracker ___ __

[issue34927] Tkinter-related segfault on macOS (regression between 3.7.0 and 3.7.1rc1)

Karthikeyan Singaravelan added the comment: Thanks, I can confirm that this works with 3.7.0 and segfaults with 3.7.1RC1 Mac OS installer that uses Tk 8.6 . Clicking the button and closing the file open dialog triggers this segfault as noted in your description. I don't know how I can config

[issue34927] Tkinter-related segfault on macOS (regression between 3.7.0 and 3.7.1rc1)

Aivar Annamaa added the comment: I got the segfault with Tk 8.6, provided with python.org installer. -- ___ Python tracker ___ ___

[issue34927] Tkinter-related segfault on macOS (regression between 3.7.0 and 3.7.1rc1)

Karthikeyan Singaravelan added the comment: Thanks for the report and script. I can't reproduce this with 3.7.1rc1 tag and also tried this on v3.7.0 which works fine on Mac OS running 10.10.4 and tcl version 8.5 . I checked out the 3.7.1rc1 tag and did a clean rebuild with `git clean -xdf &&

[issue34927] Tkinter-related segfault on macOS (regression between 3.7.0 and 3.7.1rc1)

Aivar Annamaa added the comment: Looks like the workaround is to provide explicit `parent` named argument to the dialog call. -- ___ Python tracker ___ __

[issue34927] Tkinter-related segfault on macOS (regression between 3.7.0 and 3.7.1rc1)

Aivar Annamaa added the comment: Here is a simple application that also exposes this problem. Click at the button and press Escape when dialog appears. import tkinter as tk import tkinter.filedialog as fd root = tk.Tk() def dostuff(): fd.askopenfile() bt = tk.Button(root, text="Clic

[issue34927] Tkinter-related segfault on macOS (regression between 3.7.0 and 3.7.1rc1)

New submission from Aivar Annamaa : After switching from Python 3.7.0 to 3.7.1rc1 (macOS, 64-bit only downloaded from python.org), my rather big Tkinter application started to segfault whenever I close a system dialog (eg. the one created by askopenfilename or showerror) by keypress (eg. Esca