Bug 100234 - Konqueror takes 100% CPU while doing ispell checking form data and hangs up
Summary: Konqueror takes 100% CPU while doing ispell checking form data and hangs up
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: khtml forms (show other bugs)
Version: 3.4
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
: 94431 102362 102771 105559 105601 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-02-25 11:02 UTC by flstcboy
Modified: 2008-06-24 12:06 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description flstcboy 2005-02-25 11:02:06 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources
OS:                Linux

Konqueror hangs up while entering online banking form data on website "Deutsche Bank". konqueror opens an ispell (spell checking) thread and takes 100% CPU. after some time i have to kill the konqueror process.
Comment 1 Tommi Tervo 2005-05-13 14:49:44 UTC
*** Bug 105601 has been marked as a duplicate of this bug. ***
Comment 2 Roland Wolters 2005-05-13 16:04:56 UTC
Similar behaviour for me - please check if it only happens when you input text into the textarea with the character-countdown, on the website called: "Verwendungszweck".

Do you have any problems with other javascript input fields, like on wikipedia, forums or weblogs?
Comment 3 Roland Wolters 2005-05-13 16:11:10 UTC
Forgot something: it really seems that the problem depends on javascript and not on the textarea-tags.
For example: the "Deutsche Bank" website has this html-code:

<tr><td colspan="3">Verwendungszweck  (z.B. Kunden-Referenznummer, max. 108 
 Zeichen)&nbsp;<span class="optional">(optional)</span></td></tr> 
 <tr><td colspan="3" class="formSet roll2"> 
 <textarea onkeydown="checkLength(this);" rows="2" id="Usage" wrap="virtual" 
 onchange="checkLength(this);" class="roll2" onfocus="checkLength(this);" 
 onkeyup="checkLength(this);" name="Usage"></textarea> 
 
 <script type="text/javascript">showMaxChars('&nbsp;Zeichen stehen noch zur 
 Verf&uuml;gung');</script></td></tr> 

There konqueror hungs up for several seconds.
But while I'm typing this text into the textarea-field of bugs.kde.org I have no problems.

I sometimes have small problems with input fields, too, like on wikipedia, on a invision power board, on a weblog, ...
These problems are not so important because it just hungs for milliseconds, but it is enough to recognize it, and it is enough to be annoied.
Comment 4 Harri Porten 2005-05-22 21:54:57 UTC
*** Bug 105559 has been marked as a duplicate of this bug. ***
Comment 5 Harri Porten 2005-05-22 21:56:23 UTC
*** Bug 102362 has been marked as a duplicate of this bug. ***
Comment 6 Roland Wolters 2005-05-22 23:13:46 UTC
I think the Bug 102362 about http://mts.ru/sms is about javascript, too, because after input one char my konqueror freezes until the char-counting field increases. And the function to increase the count-field is a java-script function.
Comment 7 Roland Wolters 2005-05-23 15:45:07 UTC
Hm, could be that these are two different problems?
Maybe the first problem depending on java-script and the second problem depending on spellchecking? Because I sometimes have very short lags while I write in kmail, too - and there is no java-script, or is it?
Comment 8 Tommi Tervo 2005-05-30 15:27:10 UTC
*** Bug 94431 has been marked as a duplicate of this bug. ***
Comment 9 Matthieu Robin 2005-05-30 18:34:13 UTC
*** This bug has been confirmed by popular vote. ***
Comment 10 Roland Wolters 2005-05-31 16:09:43 UTC
I now use KDE 3.4.1, and it seems that the bug has disappeared at least at:
- Wikipedia
- Deutsche Bank
- kmail
- http://mts.ru/sms
- blogger.com.

I only still have this problem rarely on an "invision board" forum.
Comment 11 Roland Wolters 2005-06-08 01:45:55 UTC
I have to take back my last post - I still have much problems on wikipedia, kmail and my blogg.
So It hink only the kjs part is solved, but not the rest. Shouldn't this bug devided into two parts? One is the kjs bug which seems to be solved, one is the annoiying bug about typing in fields.
Comment 12 Tommi Tervo 2005-06-15 13:08:22 UTC
*** Bug 102771 has been marked as a duplicate of this bug. ***
Comment 13 Roland Wolters 2005-06-23 01:39:06 UTC
Well, I tested this problem on several machines:
the js bug is away since kde 3.4.1, thanks very much.

The other bug is still there, but on my (new) fc4 it seems that it depends on the graphic-driver I use:
If I use radeon, everything is allright, if I use fglrx, I have the problems while typing in wikipedia, blog, kmail, ...

Can someone confirm this behaviour?
Comment 14 Roland Wolters 2005-06-24 01:45:47 UTC
Please check Bug #95302 for all problems with slow input fields which do not belong to kjs!
Comment 15 Sebastian Stein 2005-06-27 00:03:05 UTC
I can confirm this bug with KDE 3.4.1. It happens for example in a webmailer interface I'm using. There is no Javascript in it, the textarea code just looks like:

         &nbsp;&nbsp;<textarea name="body" id="body" rows="20" cols="76" wrap="virtual">


</textarea><br />

But I can also reproduce it with this textarea field here on bugs.kde.org. I just have to highlight some text with the mouse, move the mouse a little but up and down, left and right but without scrolling the whole textarea and konqueror will freeze for some seconds. The "top" command gives me the following output while konqueror is frozen:

 2719 root      15   0 25272  14m 2136 S  1.7  5.9   1:22.41 X                     
 2814 sstein    15   0 27648  15m  12m S  0.7  6.4   0:04.94 kwin                  
 3815 sstein    16   0  2064 1076  832 R  0.7  0.4   0:00.09 top                   
 2795 sstein    15   0 48700  19m  14m S  0.3  7.8   0:06.13 kded                  
 3463 sstein    15   0 53508  33m  19m S  0.3 13.3   0:15.57 konqueror             
    1 root      16   0   668  228  200 S  0.0  0.1   0:00.81 init                  
    2 root      34  19     0    0    0 S  0.0  0.0   0:01.61 ksoftirqd/0           
    3 root      10  -5     0    0    0 S  0.0  0.0   0:00.12 events/0              
    4 root      11  -5     0    0    0 S  0.0  0.0   0:00.01 khelper               
    9 root      15  -5     0    0    0 S  0.0  0.0   0:00.00 kthread               
   17 root      10  -5     0    0    0 S  0.0  0.0   0:00.13 kacpid                
  103 root      10  -5     0    0    0 S  0.0  0.0   0:00.05 kblockd/0             
  198 root      20   0     0    0    0 S  0.0  0.0   0:00.00 pdflush               
  199 root      15   0     0    0    0 S  0.0  0.0   0:00.17 pdflush               
  117 root      15   0     0    0    0 S  0.0  0.0   0:00.11 khubd                 
  200 root      15   0     0    0    0 S  0.0  0.0   0:00.45 kswapd0               
  201 root      16  -5     0    0    0 S  0.0  0.0   0:00.00 aio/0                 
  282 root      25   0     0    0    0 S  0.0  0.0   0:00.00 kseriod               

So it is not like that it takes all CPU or mem. I hope this really helps, because this is a very ugly bug which really hurts the overall user experience.

Sebastian
Comment 16 Sebastien Renard 2005-06-27 12:26:16 UTC
Full ACK ! I've got exactly the same pb. No cpu for X but a freeze of konqui. It only happen if I play with the mouse. No pb if I use keyboard only.

It is not related to X driver (got the pb with nvidia and ati) and do not seems to be related to javascript (this textarea, in buzilla, cause the bug too).

It is quite painfull ; Konqueror is almost unusable for a webmail. I have to switch to firefox (sic !) to do this.
No pb with KDE 3.3.x. I try to upgrade from qt 3.3.3 to qt 3.3.4 with the bug is still there.
Comment 17 Roland Wolters 2005-06-27 23:18:18 UTC
Please check this bug: #95302
There is a workaround given for ati-drivers.

In this bug here there are two different problems described (first: kjs, second: textarea), someone should close this bug and links to #95302 for the textarea problem.
Comment 18 Sebastian Stein 2005-06-27 23:37:47 UTC
I'm not sure if this is really a duplicate of #95302. I can't see a reason why this should depend on a graphic driver. I'm using for example a standard xorg driver without any special settings. So I think a developer with more insight should decide, if both problems are related to each other.
Comment 19 Roland Wolters 2005-07-05 16:06:23 UTC
@Sebastian Stein: I think that you are right - your description is totally different from that what I've seen.
It seems (to me) that you have a "new" bug - not related to kjs (as this bug originally was and what is solved with kde 3.4.1), not related to 3D X-drivers (which is described in #95302 and has a workaround there) but realted to textarea fields.

What's about starting a new bug?

I must say that I am a little bit disappointed that no developer answered to some of these bugs...
Comment 20 Sebastian Stein 2005-07-15 17:49:30 UTC
@Roland Wolters: I was able to resolve the problem with the textarea by disabling the option in klipper to save klipper content at exit. This is described in bug #96639.

So people say the JS part of the bug was resolved? Should we now close the whole report?

Sebastian
Comment 21 Roland Wolters 2005-07-17 12:41:10 UTC
It solved my problem, too - so for me there are two working workarounds: the one with klipper and the one with the graphic drivers.

For me the bug can be half closed, half marked as a duplicate of Bug #91357 .
Comment 22 Roland Wolters 2005-10-22 20:06:05 UTC
Tested on a SUSE LINUX 10.0 with KDE 3.5beta2:
The problem is still there, without graphic drivers. I deactivated the option in klipper to save klipper content at exit, and not the problem is gone.
Comment 23 FiNeX 2008-04-20 20:46:27 UTC
I've got no problem with textarea on konqueror 4.
Comment 24 A. Spehr 2008-06-24 12:06:50 UTC
closing; can't confirm in 4.00.83