Bug 74771

Summary:	marking text in forms hangs konqueror
Product:	[Applications] konqueror	Reporter:	Fred Wells <fredcwells>
Component:	khtml forms	Assignee:	Konqueror Bugs <konqueror-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Fred Wells 2004-02-09 23:00:25 UTC

Version:           3.2.0 (using KDE 3.2.0, compiled sources)
Compiler:          gcc version 3.2.2 (Mandrake Linux 9.1 3.2.2-3mdk)
OS:          Linux (i686) release 2.4.21-0.25mdkenterprise

Marking/updating text in text box intermittently hangs 
konqueror for long periods of time (many seconds).

To reproduce, open a form with a simple text box. Then, in
quick succession, continue to mark, add, delete and modify 
the contents of the box. Eventually, konqueror will hang 
for several seconds.  The successive behavior isn't always
necessary.  Simple changes have also caused it to hang.
In fact, just updating this bug report has already caused it 
to hang once for me.

Comment 1 Fred Wells 2004-03-12 05:14:05 UTC

Still there in kde3.2.1.

Comment 2 Leon Bottou 2004-04-20 16:36:14 UTC

Same thing here.
I was checking the bugs database for a fix.

There are many reports of that kind.
Some are closed because there one suspects
an elusive kernel bug or X driver bug.
But there is a pattern here...

This might be related to a form of X server grab.
When there is such a hang, focus-follows-mouse no longer works.  
I can still click into a konsole and execute commands.
On the other hand, clicks on the kicker icons do nothing.
After a few seconds, all my lost clicks are replayed
(as if using XAllowEvents after a X server grab)
and everything is back to normal...

Using Redhat8 + FedoraLegacy + KDE-Redhat (3.2.1).

Question: This seems a complex interaction bug.
KDE seems to do something that triggers the problem.  
How to instrument the code and obtain more information?
- L.

Comment 3 Fred Wells 2004-05-13 19:48:53 UTC

Still broke in 3.2.2.  BTW - this bug was introduced in kde3.2.x, i.e. it didn't exist prior and my X configuration hasn't changed.  Perhaps some review of 3.2.x code changes related to this KDE/X interaction is necessary.

Comment 4 Tommi Tervo 2004-05-13 20:50:15 UTC


*** This bug has been marked as a duplicate of 80072 ***