disable send -> X error on exit

Logged In: YES
user_id=80530
Originator: YES

This appears to be the same issue:

http://objectmix.com/tcl/250971-bug-8-5b1.html

Logged In: YES
user_id=80530
Originator: YES

Haven't fully tracked it down yet, but
the saga of 1712081 is involved somehow.

Logged In: YES
user_id=80530
Originator: YES

Ok, now I think 1712081 has nothing to
do with it, so withdraw that claim first.

The trouble first arises with
Kevin Kenny's 2006-11-27 commit to
unix/configure(.in).

All that change really does, though, is
to change from a --disable-xft default
build to a --enable-xft default build
in my current test environment.

Sure enough if I force a --disable-xft
build of Tk 8.5-HEAD, and use that, the
problem goes away.

Logged In: YES
user_id=99768
Originator: NO

While I committed the change that makes --enable-xft the default, that was on the basis of (a) it's now nearly-universal in Linux distros, and (b) Tk looks like hell without it. Beyond those two factoids, I'm extremely ignorant of what goes on inside. (If it were the *non*-Xft build failing, I'd feel more competent to have a look.)

Referring to someone who might have a clue how to approach debugging this.

Logged In: YES
user_id=68433
Originator: NO

Duplicate of #1821174.

Cause of the problem: Tk's teardown sequence sets tsdPtr->displayList to NULL before calling TkpCloseDisplay on each member of the list, so if any X errors occur during the final XSync(), ErrorProc is not able to dispatch them to the correct TkErrorHandler.

The RenderBadPicture error is raised in response to XftDrawDestroy() when the Drawable associated with the XftDraw has been destroyed before the XftDraw itself is. This call (in FinishedWithFont, in tkUnixRFont.c) is bracketed by Tk_CreateErrorHandler / Tk_DeleteErrorHandler, so would not be a fatal error, except for the problem above.

Removing the [send] command causes (among other things) an XSync() to occur; this normally occurs at a point in Tk's teardown sequence where it happens to mask the above two problems. If the application removes [send] itself earlier, this doesn't happen, and the problem manifests.