On Mon, 26 May 2008 04:05:28 +0800, David W. Hodgins
a look at this thread?
I'm not Opera staff, but I've had a look at it anyway.
The problem only occurs when the page is loaded from the site and it
doesn't already exist in the cache. Once it's in Opera's cache, the
problem does not occur. If the page is loaded fresh then you get 100% CPU.
Reloading from cache fixes that, as does a regular reload. Closing the
browser and restarting it at that point does not invoke the problem
either, unless you empty the cache before re-opening the site. If the
Google Analytics script).
My suspicion is the "document.onmousemove = mouseMove;" line. The reason
being that this line will likely execute before the page content
(document) it's registering on has actually loaded. When loading from
cache, it's likely the document is whipped out of the cache and created
before the JS executes. I'd move that event registration into an "onload"
handler and see what happens.
<URL: http://www.scss.com.au/family/andrew/ >