RequestAnimationFrame "sinchronisation"?

[Evgeny Demidov]

sorry for off-topic (I didn't get the answer in WebCL or Nvidia OpenCL forums yet).
Since FF7 all my MC WebCL based simulations freeze in a while with CL_INVALID_KERNEL_ARGS error. See simple test
http://www.ibiblio.o...cl/nokia3a.html
it just executes in an infinite cycle

 function run() {
                  cmdQueue.enqueueNDRangeKernel(kernel, 1, [], [32], [8], []);
                  cmdQueue.finish();
                  iter++;
                  output.innerHTML = "<br>" + iter;
   setTimeout("requestAnimFrame(run)", 100);
 }          
The kernel just makes C[] = A[] + B[]
Sometimes the scripts works fine, sometimes freezes after 20 - 100 iterations. It makes easily 10000-100000 iterations in simple cycle if I comment  "requestAnimFrame" operator. Why "requestAnimFrame" may be dangerous (after FF 6) ?
Any suggestions how can I debug my script?

Evgeny Demidov

Error: WebCLCommandQueue::EnqueueNDRangeKernel Failed with error -52.

[Mark Callow]

On 22/06/2012 13:29, Evgeny Demidov wrote:

function run() {
                  cmdQueue.enqueueNDRangeKernel(kernel, 1, [], [32], [8], []);
                  cmdQueue.finish();
                  iter++;
                  output.innerHTML = "<br>" + iter;
   setTimeout("requestAnimFrame(run)", 100);
 }          
The kernel just makes C[] = A[] + B[]
Sometimes the scripts works fine, sometimes freezes after 20 - 100 iterations. It makes easily 10000-100000 iterations in simple cycle if I comment  "requestAnimFrame" operator. Why "requestAnimFrame" may be dangerous (after FF 6) ?

Probably they aren't expecting requestAnimFrame to be run from a timer.

Are you using the requestAnimFrame from WebGLUtils? The browser function, when it exists, is requestAnimationFrame(). WebGLUtils' requestAnimFrame uses requestAnimationFrame() when it exists, otherwise it uses a timer. Timer to timer is also likely an unexpected behaviour.

Regards

    -Mark

[Evgeny Demidov]

function run() {
                  cmdQueue.enqueueNDRangeKernel(kernel, 1, [], [32], [8], []);
                  cmdQueue.finish();
                  iter++;
                  output.innerHTML = "<br>" + iter;
   setTimeout("requestAnimFrame(run)", 100);
 }          
The kernel just makes C[] = A[] + B[]
Sometimes the scripts works fine, sometimes freezes after 20 - 100 iterations. It makes easily 10000-100000 iterations in simple cycle if I comment  "requestAnimFrame" operator. Why "requestAnimFrame" may be dangerous (after FF 6) ?

Are you using the requestAnimFrame from WebGLUtils? The browser function, when it exists, is requestAnimationFrame(). WebGLUtils' requestAnimFrame uses requestAnimationFrame() when it exists, otherwise it uses a timer. Timer to timer is also likely an unexpected behaviour.

I'm using (as in all WebGL scripts) the shim:
requestAnimFrame = (function(){
  return  window.webkitRequestAnimationFrame ||
    window.mozRequestAnimationFrame ||
    function(callback, element){ window.setTimeout(callback, 1000 / 60); }
})();

Scripts freeze without "setTimeout(...)" too. All worked fine in FF4 - 6, therefore I think it is a question to Mozila team.

Evgeny