© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I believe the issue can be narrowed down to page cache resource expiration times being invalidated when a previous page is loaded. If this is true, then a manual reload of the page should stop the continuous page redraws:
Test:
1. Start midori with no more than one page loaded
2. Load a relatively static web page: (eg: www.debian.org)
3. Using top or htop observe the avg midori cpu usage. It should settle down to 0%
4. Open a new tab on www.debian.org. Observe that avg cpu usage is still 0% after a few seconds
5. Select the first tab. Observe avg cpu usage rises to approximately 35%
6. Force a reload on that page
7. Observe that the avg cpu usage returns to 0%
8. Select the second tab
9. Observe that the avg cpu usage again climbs to 35%
10. Force a reload on the page
11. Observe that the avg cpu usage drops to 0%
This very likely has something to do with the cache expiration time on an existing web page either being invalidated when it is no longer the current page or when a pre-existing web page is brought back into view.
Can someone look at the page resource expiration times or check the expiration and resource reload code to see if there's a bug in there somewhere? Could this have crept into webkit in between versions?
Two issues:
1. I don't know what this has to do with an upgrade from gtk2 to gtk3, but there's probably some interaction or patch that's breaking this.
2. A couple links that I've seen to the same type of issue in maxthon and safari are the following:
http://
(search for 'resource reload')
http://