| Summary: | Konqueror takes 100% CPU while doing ispell checking form data and hangs up | ||
|---|---|---|---|
| Product: | [Applications] konqueror | Reporter: | flstcboy |
| Component: | khtml forms | Assignee: | Konqueror Developers <konq-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | anders.lund, artem, finex, jerome, rolandwolters, seb.kde, tristan, zahl |
| Priority: | NOR | ||
| Version: | 3.4 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
flstcboy
2005-02-25 11:02:06 UTC
*** Bug 105601 has been marked as a duplicate of this bug. *** 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? 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) <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(' Zeichen stehen noch zur
Verfü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.
*** Bug 105559 has been marked as a duplicate of this bug. *** *** Bug 102362 has been marked as a duplicate of this bug. *** 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. 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? *** Bug 94431 has been marked as a duplicate of this bug. *** *** This bug has been confirmed by popular vote. *** 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. 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. *** Bug 102771 has been marked as a duplicate of this bug. *** 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? Please check Bug #95302 for all problems with slow input fields which do not belong to kjs! 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:
<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
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. 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. 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. @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... @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 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 . 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. I've got no problem with textarea on konqueror 4. closing; can't confirm in 4.00.83 |