OriginalBugID: 2067 Bug
OS: Linux-Red Hat
Name: Patrick Earl
Tcl/Tk were compiled with --enable-shared --enable-gcc on pgcc-2.91.60
I have a Tk app (quirc.org) that I frequently paste large pieces of text
into, and the slow (or frozen) behaviour of the entry box is annoying at
echo "pack [entry .test]" | wish8.1
There are a number of problems that occur when I do one of the
1) Paste a large amount of text into the entry box (ex. >2k) and hit
2) Type for an extended period of time into the entry box.
3) Paste a fair amount of text into an already selected area of text.
1) Freezes the app with 100% CPU usage
2) The entry box becomes sluggish and does not update itself as it needs
to. It becomes slower and slower as one types more text. I typed a
couple paragraphs in it, and it was practically unusable for text entry
at that point.
3) I took a selection of 80 characters of text, pasted it within the
entry box a single time. Then I selected what I had just pasted and
proceeded to simply paste within the existing selection. After around 7
pastes, there was noticeable CPU usage. The CPU usage disappears when
the window is not in focus.
The CPU usage increased up until about 11 pastes where it was taking up
around 100% CPU. I did 12 pastes, then changed the focus to another
window, and then back to this one, and I got the following error (with
X Error of failed request: BadLength (poly request too large or
internal Xlib length error)
Major opcode of failed request: 74 (X_PolyText8)
Serial number of failed request: 5800
Current serial number in output stream: 5808
If I paste a bunch of times after 12 without letting the window leave
focus, it goes into a state of 100% CPU usage and does not seem to stop
without killing wish.
1) It should not freeze, but should simply go to the end of the pasted
2) Should not slow down, should continue entering text at normal speeds.
3) It should not freeze or consume large amounts of CPU, but should
continue to allow pasting and entry of text as normal.
There is an obvious slowdown in the action wizards using entry widgets when the user types really fast in an entry. This was part of the problems observed in # 3150 (the other issues have been resolved).
-- 10/29/1999 sven
This was do to an overeager while calculation in tkEntrySeeInsert.
This has been changed for 8.2.2, slightly altering the behavior
when moving the cursor in the entry widget (for the better, IMO).
-- 10/29/1999 hobbs