Hello! www-client/midori-0.4.8 consumes too much CPU time after a page is loaded. Here by "too much" I mean "consumes about 90% of CPU time for 10 seconds and often more". And sometimes it keeps consuming ~90% of CPU with only speed-dial page open for virtually infinite time. In fact, I observed similar behaviour for some older versions as well, and made a bugreport about that upstream, but it looks like "nobody cares"™. So it made me think that this may be actually a Gentoo-specific problem, and I decided to create a bugreport here. It also turned out that if I start Midori like this: midori -a http://website-address it works fine (i.e. does not consume so much CPU time). At first I thought it was because of the Webkit-GTK or GTK3, but now I use also Xombrero browser built against the very same versions of Webkit-GTK and GTK3, and it does not manifest such strange behaviour. Reproducible: Always Steps to Reproduce: 1. Start 'top' 2. Start midori and open some websites (especially the "heavy" ones like tex.stackexchange.com) and watch the CPU usage in 'top'. 3. Try to open some new page and scroll up and down while it is loading. Notice how long Midori is 'hung' even after the page is loaded. 4. Try starting Midori with 'midori -a <website_address>' parameter and see how fast it works with the same sites.
I cannot reproduce this with 0.5.0. Does the problem still exist?
(In reply to comment #1) > I cannot reproduce this with 0.5.0. Does the problem still exist? I concur. Reporter should test 0.5.0 and move this to upstream bug tracking system.
(In reply to comment #2) > I concur. Reporter should test 0.5.0 and move this to upstream bug tracking > system. This bug has been reported upstream: https://bugs.launchpad.net/midori/+bug/1103102
