test_idle causes test_ttk_guionly 'can't invoke "event" command: application has been destroyed' messages from Tk

[ned-deily]

BPO	20567
Nosy	@terryjreedy, @kbkaiser, @ned-deily, @serwy, @serhiy-storchaka
Files	issue20567.patch

^{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/terryjreedy'
closed_at = <Date 2016-06-04.02:31:15.370>
created_at = <Date 2014-02-08.23:36:17.984>
labels = ['tests', 'expert-IDLE', 'type-bug', 'expert-tkinter']
title = 'test_idle causes test_ttk_guionly \'can\'t invoke "event" command: application has been destroyed\' messages from Tk'
updated_at = <Date 2016-06-04.06:33:38.211>
user = 'https://github.com/ned-deily'

bugs.python.org fields:

activity = <Date 2016-06-04.06:33:38.211>
actor = 'terry.reedy'
assignee = 'terry.reedy'
closed = True
closed_date = <Date 2016-06-04.02:31:15.370>
closer = 'terry.reedy'
components = ['IDLE', 'Tests', 'Tkinter']
creation = <Date 2014-02-08.23:36:17.984>
creator = 'ned.deily'
dependencies = []
files = ['34011']
hgrepos = []
issue_num = 20567
keywords = ['patch']
message_count = 23.0
messages = ['210704', '210738', '210745', '210746', '210749', '210769', '210772', '210776', '212331', '212396', '212398', '219528', '221467', '226217', '229182', '229201', '229224', '267116', '267117', '267223', '267227', '267230', '267237']
nosy_count = 7.0
nosy_names = ['terry.reedy', 'kbk', 'ned.deily', 'roger.serwy', 'python-dev', 'serhiy.storchaka', 'andtorg']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue20567'
versions = ['Python 2.7', 'Python 3.4', 'Python 3.5', 'Python 3.6']

[ned-deily]

Seen with default (3.4.0) framework builds on OS X 10.9 with ActiveTcl 8.5.15.0:

./configure --enable-universalsdk=/ --with-universal-archs=intel --enable-framework=/tmp/t/Library/Frameworks
make && make install
cd /tmp/t
/tmp/t/bin/python3.4 -m test -w -uall
[...]
[343/389/1] test_ttk_guionly
can't invoke "event" command: application has been destroyed
while executing
"event generate $w <<ThemeChanged>>"
(procedure "ttk::ThemeChanged" line 6)
invoked from within
"ttk::ThemeChanged"
can't invoke "event" command: application has been destroyed
while executing
"event generate $w <<ThemeChanged>>"
(procedure "ttk::ThemeChanged" line 6)
invoked from within
"ttk::ThemeChanged"
can't invoke "event" command: application has been destroyed
while executing
"event generate $w <<ThemeChanged>>"
(procedure "ttk::ThemeChanged" line 6)
invoked from within
"ttk::ThemeChanged"
can't invoke "event" command: application has been destroyed
while executing
"event generate $w <<ThemeChanged>>"
(procedure "ttk::ThemeChanged" line 6)
invoked from within
"ttk::ThemeChanged"
[344/389/1] test_ttk_textonly
[...]

When running test_ttk_guionly by itself (or in combination with a few neighboring tests):

/tmp/t/bin/python3.4 -m test -w -uall test_ttk_guionly

the message is not seen. I had not seen this behavior prior to somewhere in the 3.4.0 development cycle.

[serhiy-storchaka]

Could you try test_ttk_guionly after test_all, test_builtins, test_tcl? If the issue is not reproduced, try to use binary search: divide the tests before test_ttk_guionly on to parts, and run tests with one half, then with other. Repeat until found the culprit.

[serhiy-storchaka]

Threading and subprocess tests also evoke a suspicion.

[ned-deily]

$ /usr/local/bin/python3.3 -m test -w -uall test_idle test_ttk_guionly
[1/2] test_idle
[2/2] test_ttk_guionly
can't invoke "event" command:  application has been destroyed
    while executing
"event generate $w <<ThemeChanged>>"
    (procedure "ttk::ThemeChanged" line 6)
    invoked from within
"ttk::ThemeChanged"
can't invoke "event" command:  application has been destroyed
    while executing
"event generate $w <<ThemeChanged>>"
    (procedure "ttk::ThemeChanged" line 6)
    invoked from within
"ttk::ThemeChanged"
can't invoke "event" command:  application has been destroyed
    while executing
"event generate $w <<ThemeChanged>>"
    (procedure "ttk::ThemeChanged" line 6)
    invoked from within
"ttk::ThemeChanged"
can't invoke "event" command:  application has been destroyed
    while executing
"event generate $w <<ThemeChanged>>"
    (procedure "ttk::ThemeChanged" line 6)
    invoked from within
"ttk::ThemeChanged"
All 2 tests OK.

[ned-deily]

The combination of just test_idle followed by test_ttk_guionly also produces the "application has been destroyed" messages on Debian Linux and when run from a build directory (e.g. not installed) and with 2.7, 3.3, and default.

[terryjreedy]

Ned, do you actually *see* this on 2.7, 3.3? The message looks suspiciously like the somewhat strange 3.4-only shutdown message suppressed by bpo-20167.

[serhiy-storchaka]

Here is a patch which fixes symptoms. Maybe we'll find better solution.

These messages are produced when the ttk::ThemeChanged command called from a callback for already destroyed Tk root window.

[terryjreedy]

Running just the two tests fails on windows also, with all three versions. For 2.7, test_ttk_guionly is skipped with "test_ttk_guionly skipped -- tk not available: Can't find a usable init.tcl in the following directories:. This in spite of the fact that the idle test just found init.tcl and that the ttk test passes without the idle test running first. This is relatively recent.

Does the test runner not delete modules as they are finished?

I am rebuilding python and will try tests again. If problem persists and patch solves it, I will go ahead and apply.

[terryjreedy]

Patch fixes problem on 3.3. I need to test 2.7 and add a note to idle_test/README that class widget attributes must be deleted because module may not be deleted, at least for a while.