HTML5 - Web Worker test on chrome for Android on Galaxy Nexus ICS

[saldy]

Looks like chrome for android runs out of memory while running image processing test on peacekeeper with web worker on Galaxy Nexus ICS with 1GB of RAM. Peacekeeper is using 4 threads to do image processing and the chrome for android browser shows sad tab.

Debugging further it looks like this particular test takes around 500MB of RAM which feels like an overkill for test for mobile device. Have we considered changing this test on a use case which do not require this much memory?

[Jarnis]

Looks like chrome for android runs out of memory while running image processing test on peacekeeper with web worker on Galaxy Nexus ICS with 1GB of RAM. Peacekeeper is using 4 threads to do image processing and the chrome for android browser shows sad tab.

Debugging further it looks like this particular test takes around 500MB of RAM which feels like an overkill for test for mobile device. Have we considered changing this test on a use case which do not require this much memory?

I believe that Peacekeeper normally is flagged to not run this test on devices that cannot run it but that naturally requires that such devices are manually added to list of setups that should skip it. Can you post the browser identification string for yours?

[androidfreak]

I believe that Peacekeeper normally is flagged to not run this test on devices that cannot run it but that naturally requires that such devices are manually added to list of setups that should skip it. Can you post the browser identification string for yours?

How can we add devices to the list ? Is there an alternate way to configure the browser/device so that I does not run the web worker tests?

[Jarnis]

There is no way for the end users to configure what tests are run. We can add problematic (mobile) devices to the list on the server side at our end but that's it.

[androidfreak]

I believe that Peacekeeper normally is flagged to not run this test on devices that cannot run it but that naturally requires that such devices are manually added to list of setups that should skip it. Can you post the browser identification string for yours?

Will listing out the device result in poorer score ? How will this impact the comparison to the other browsers. Is there a way that we could know which other devices fall in the same category so that its easier to compare?