search

soundcloud / areweplayingyet

html5 audio benchmarks
BSD 2-Clause "Simplified" License
311 stars 69 forks source link

high cpu load after running all tests? #36

Open MrX1980 opened 12 years ago

MrX1980 commented 12 years ago

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?

yvg commented 12 years ago

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?

MrX1980 commented 12 years ago

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

With Google Chrome -> JavaScript Console -> Network: http://areweplayingyet.herokuapp.com/sounds/short.mp3?[SessionID] Status = canceled Type = undefined Time = pending

I hope this can help.

yvg commented 12 years ago

Did you try my proposed change locally? I didn't update the live code.

MrX1980 commented 12 years ago

Oh, I have tried the live code. How I can try the local code?

yvg commented 12 years ago

As explained in the readme here: https://github.com/soundcloud/areweplayingyet