Bug 77618

Summary: Konqueror stops responding when browsing www sites, no problems with 3.2.0
Product: [Applications] konqueror Reporter: Jarkko Haapalainen <jarkko.haapalainen>
Component: generalAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:

Description Jarkko Haapalainen 2004-03-14 23:49:15 UTC
Version:            (using KDE KDE 3.2.1)
Installed from:    Gentoo Packages
Compiler:          gcc version 3.3.3 20040217 (Gentoo Linux 3.3.3, propolice-3.3-7) 
OS:          Linux

This bug is annoying and hard to produce exactly.

About one of ten www sites konqueror stops responding and I have to wait about 2-3 seconds to get control of konqueror.

So far it has happens only when browsing www sites.

I had no problems with KDE 3.2.0 and I had to change back to that version for now. So the problem has to be in changes from 3.2.0 to 3.2.1.
Comment 1 Sashmit Bhaduri 2004-03-16 08:01:29 UTC
Can't do much without more info.. what websites?
Comment 2 Jarkko Haapalainen 2004-03-16 08:23:21 UTC
It's not any specific web site.. I'll try get some more info. I'm now compiling KDE 3.2.1 with different cfags and try to figure out if the problem was there. Thought I don't have any problems with 3.2.0.
Comment 3 Jarkko Haapalainen 2004-03-17 07:18:46 UTC
Solved this by removing all ~/.kde* files. Don't know what I did with KDE configuration to get this kind of behaviour. Closing this bug for now..
Comment 4 Piotr Szymański 2004-09-12 19:28:54 UTC
This bug wasnt fixed, removing .kde is a stupid workaround, how can one expect users to remove their configs ever 3.x release?

This happens on:
- http://teodozjan.jogger.pl
- http://www.opencroquet.org

I will add more sites once I encounter them. Also I will gladly provide any kind of gdb/valgrind output you ask for. 
Also not sure this should be a konqueror/general bug, but cant make sure its khtml's fault. Only thing I am sure is that it is not related to kjs or ecma, since it happens with them disabled.
Comment 5 Piotr Szymański 2004-09-12 19:32:28 UTC
This only happens on KDE_3_3_BRANCH and current HEAD, not on KDE_3_3_0_RELEASE. At least here.
Comment 6 Maksim Orlovich 2004-11-15 21:34:40 UTC

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