Closed Bug 154373 Opened 23 years ago Closed 23 years ago

CPU remains at 100% after www.aftonbladet.se

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 146884

People

(Reporter: markushuebner, Assigned: Matti)

References

()

Details

(Keywords: regression)

Do shift-reload a few times (3 times here) ... then at the last time the status bar remains "transferring data from www.aftonbladet.se ..." and the CPU usage remains 100%! If you go now for example to www.mozilla.org there is this message in the status bar "transferring data from www.mozilla.org ..." with cpu usage all the time at 100%. Mozilla then never get's down again. using trunk build 2002062508 on win-xp
Keywords: perf, regression
wfm with win2k build 20020626..
Keywords: perf
Testing trunk build 2002062608 on win-xp,1.1ghz,512RAM I get 100% CPU usage also the very first time I get to this page - so without any reload. It remains there also when I leave the page. Just having open the Navigator (no Mail etc.).
Summary: CPU remains at 100% after reloading http://www.aftonbladet.se few times → CPU remains at 100% http://www.aftonbladet.se few times
Cannot reproduce this with build 20020625 using Windows 2000 Pro. The CPU goes up to 100% every time I load a new page, but it does the same on IE 6. I guess its because the nightmare html-code + all the flash banners. Maybe its XP only that the CPU remains at 100%. About the "Transferring data..", that is bug 133250.
Using MSIE6 I have remaining 4% cpu usage. Starting Mozilla fresh and starting with the URL http://www.aftonbladet.se/ I don't get 100%cpu ... but doing a shift-reload get's cpu usage immediately to 100% cpu and it remains there (also when going to other websites). Josè did you try shift-reload ?
Yes, tried SHIFT + reload several times. CPU always goes done afterwards.
Summary: CPU remains at 100% http://www.aftonbladet.se few times → CPU remains at 100% after www.aftonbladet.se
-> wfm wfm with win2k build 20020710..
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Testing without pipelining works fine. With pipelining still the same problems as reported.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
*** This bug has been marked as a duplicate of 146884 ***
Status: REOPENED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.