diff options
| author | Bradley T. Hughes <bradley.hughes@nokia.com> | 2009-04-08 11:07:33 +0200 |
|---|---|---|
| committer | Bradley T. Hughes <bradley.hughes@nokia.com> | 2009-04-08 11:28:06 +0200 |
| commit | 74f092408d1a870e2c1e2a49182c8e09f952055d (patch) | |
| tree | bc3fd9f069ecd84a842650ba028df6d46f850238 /dist | |
| parent | c131208e59f5b2dd517b00c4539458760b8fd8aa (diff) | |
| download | qt4-tools-74f092408d1a870e2c1e2a49182c8e09f952055d.tar.gz | |
Javascript: When there is javascript running then it will spin the CPU at 100%
Zero timers on Windows would continue to fire even after being stopped
as long as a new timer was started that reused the pointer address of
the zero timer. Fix this by only re-firing zero timers if the zero
timer hadn't been stopped (we can check this by looking at the
inTimerEvent flag, which is set to false by registerTimer()).
Task-number: 247401
Reviewed-by: Denis Dzyubenko
Reviewed-by: Prasanth Ullattil
Diffstat (limited to 'dist')
| -rw-r--r-- | dist/changes-4.5.1 | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/dist/changes-4.5.1 b/dist/changes-4.5.1 index de4eef7196..eb8ec5fa8b 100644 --- a/dist/changes-4.5.1 +++ b/dist/changes-4.5.1 @@ -68,6 +68,10 @@ Qt for Linux/X11 Qt for Windows -------------- +- QCoreApplication + * [247401] Fixed a bug that would cause a restarted timer to fire + too early, causing Javascript in QtWebKit to consume 100% CPU on + Windows. Qt for Mac OS X --------------- |