Bug 35678 - [Qt] Using Javascript timers in QWebkit results in very high CPU usage
Summary: [Qt] Using Javascript timers in QWebkit results in very high CPU usage
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Other Windows XP
: P2 Normal
Assignee: Nobody
URL:
Keywords: Qt
Depends on:
Blocks:
 
Reported: 2010-03-03 05:57 PST by Tor Arne Vestbø
Modified: 2010-03-17 07:09 PDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tor Arne Vestbø 2010-03-03 05:57:08 PST
This bug report originated from issue QTBUG-3784
http://bugreports.qt.nokia.com/browse/QTBUG-3784

--- Description ---

opening the file below with arora resulted in high CPU usage on Windows (on Linux, it works fine)


<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-xml"><span class="code-tag">&lt;!DOCTYPE html PUBLIC <span class="code-quote">"-//W3C//DTD XHTML 1.0 Transitional//EN"</span> <span class="code-quote">"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"</span>&gt;</span>
<span class="code-tag">&lt;html xmlns=<span class="code-quote">"http://www.w3.org/1999/xhtml"</span>&gt;</span>
<span class="code-tag">&lt;head&gt;</span>
    <span class="code-tag">&lt;title&gt;</span>QWebKit test<span class="code-tag">&lt;/title&gt;</span>
<span class="code-tag">&lt;script type=<span class="code-quote">"text/javascript"</span>&gt;</span>
    function nothing()
    {

    }
    window.setInterval(nothing,1000);
<span class="code-tag">&lt;/script&gt;</span>
<span class="code-tag">&lt;/head&gt;</span>

<span class="code-tag">&lt;body&gt;</span>This is a test...<span class="code-tag">&lt;/body&gt;</span>

<span class="code-tag">&lt;/html&gt;</span></pre>
</div></div>
Comment 1 Jocelyn Turcotte 2010-03-17 07:09:04 PDT
Could not reproduce in 4.5.3 and trunk on Windows 7

Please provide additional information/test case if you have any for this bug.
Resolving as work for me.