Version: (using KDE KDE 3.5.8) Installed from: Unlisted Binary Package Compiler: 4.2.2 OS: Linux while browsing facebook, especially on profiles, Konqueror apparently stops responding to anything for a reasonable (10s?) amount of time. In that time I tried maximizing the screen. When I tried to do that konqueror did not redraw, the application drawing was still the same size even though the window was larger. After waiting for a good 10s or more it redrew the page perfectly. At one point the whole GUI locked up while browsing facebook for a brief 5s or so. The machine is relatively fast and this doesn't happen elsewhere, its a dual athlon mp machine with a 1gb of mem running archlinux with 2.6.23 kernel.
Which display driver do you use, others have reported that recent nvidia drivers behaves badly on some sites (see bug #151620). Is it Xorg or konqueror which consumes CPU time?
Nah, it's not driver related, their CSS just DoS's the matching code. It has thousands of descendant classname selectors --- pretty much the worst case there is for us.
the latest nvidia driver in fact. Its definitely konqueror though. It sits there using up 50% of the cpu for a good 10-20s on average for each facebook page. A few times it would just spike to 80% and not redraw for 30s or so. -Tom On Tuesday 06 November 2007 03:50:47 am Tommi Tervo wrote: [bugs.kde.org quoted mail]
I have no issues using facebook. Do you have example profile that are particular bad?
Allan: see Alex Spehr's (or Lypanov's) profiles linked off my page. Basically, the thing has ~3000 complex descendant selectors containing very long classname selectors, and multiple nodes with many classes. I see it spending as much as 8 seconds or so doing recalcStyle, particularly since the multiple style tags seem to trigger multiple calls
I think Facebook has solved the issue themselves. Probably to improve Safari-performance. Now there is never more than one <style> element which contains all the styles for all the loaded facebook applications.
Hi, Can anyone still reproduce this bug now? Is it still valid or is it a WORKSFORME now? Thanks.
It is valid allright. Mainpage looks like this : PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 15315 sgh 20 0 241m 82m 31m S 18 9.3 3:00.33 konqueror It just keeps om going.IT never gets below 13% cpu on my system.
Maksim: So is this being kept open to remind you to fix descendant classname selectors in general someday? Or did that already happen? Or do you just want to keep open the report in which you use my fb page as a DDOS example? :D There's been a major site change at this point, so any new "facebook is slow" bugs should get a new report.
Dear user, KHTML (and KJS) was a long time more or less unmaintained and got removed in KF6. Please migrate to use a QWebEngine based HTML component. We will do no further fixes or improvements to the KF5 branches of these components beside important security fixes. For security issues, please see: https://kde.org/info/security/ Sorry that we did not fix this issue during the life-time of KHTML. Greetings Christoph Cullmann