You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
after running all tests (results are visible) I see still "high" cpu load.
Tested with Firefox Release, Beta, Aurora, Nightly; Opera Next; Google Canary and IE9.
Only IE9 seems to be ok.
On a single core cpu I have about 100% and on a six core cpu about 17%
Can you find a reason for that?
The text was updated successfully, but these errors were encountered:
Thanks @MrX1980
It seems to happen in the event-abort.js test
By checking out the git log I find out that audio.removeAttribute('src'); was replaced by audio.src = '';
By rolling this back it seems to fix the issue.
If I remember correctly we made this change because IE was crashing.
In both cases there seems to be browsers bugs here there we should report.
@MrX1980 Can you try out my change and see if it results in 100% CPU use for you?
note: awpy.js:39 also contains audio.src = ''; but doesn't seem to affect the CPU at all… @tsenart got an other idea?
Hello Yves,
I have still 100% cpu usage with Firefox Nightly, Opera Next and Chrome Canary.
IE9 is working fine.
In the error console of Firefox I have many entries of:
Warning: Invalid URI. Load of media resource failed.
Source File: http://areweplayingyet.org/
Line: 0
Hello
after running all tests (results are visible) I see still "high" cpu load.
Tested with Firefox Release, Beta, Aurora, Nightly; Opera Next; Google Canary and IE9.
Only IE9 seems to be ok.
On a single core cpu I have about 100% and on a six core cpu about 17%
Can you find a reason for that?
The text was updated successfully, but these errors were encountered: