12root2

I am trying to find a way to write a js code that involves a loop procedure, iterating a large buffer object and do some stuff with it.

I wrote a code which works fine, but shuts all other operation within the patch (patch is not responsive, sometimes even crashes).

I found out about the Task object that handles the scheduler and done some basic tests with it, and found some strange(?) behaviors.

For example, I've dug out some basic example from here --- the function purpose itself is not important---:

http://1cyjknyddcx62agyb002-c74projects.s3.amazonaws.com/files/2017/01/js_in_background.js

And it works fine. The patch is responsive and no crashes, and the process, albeit somewhat slow, is working well.

This is an example for an endless loop procedure using the possiblePrime variable increment.

However when I change the function findPrimes() to something like this:

function findPrimes(){ //// will not calculate the prime. This is only for the sake of experimenting...

The patch changes its behavior drastically and become not responsive and with bigger iterations count even crash.

This, despite all I've done is to "phrase" the loop procedure differently, (even more so, I've bounded it to a finite number of iterations!).

Why is this happening, and what can I do in order to write a better code? (without taking apart every increment...)

I am trying to find a way to write a js code that involves a loop procedure, iterating a large buffer object and do some stuff with it.
I wrote a code which works fine, but shuts all other operation within the patch (patch is not responsive, sometimes even crashes).

For example, I've dug out some basic example from here --- the function purpose itself is not important---:
http://1cyjknyddcx62agyb002-c74projects.s3.amazonaws.com/files/2017/01/js_in_background.js
And it works fine. The patch is responsive and no crashes, and the process, albeit somewhat slow, is working  well.
This is an example for an endless loop procedure using the possiblePrime variable increment. 

function findPrimes(){     //// will not calculate the prime. This is only for the sake of experimenting...
    for (i=0; i
        outlet(0,i);
    }
}

The patch changes its behavior drastically and become not responsive and with bigger iterations count even crash.
This, despite all I've done is to "phrase" the loop procedure differently, (even more so, I've bounded it to a finite number of iterations!).

js-task-object-behavior-under-long-procedural-loop

The original function called outlet() at most once per task execution. Your patch calls outlet() 99999999 times per task execution. Which means, max tries to process the max objects connected to the outlet outside of the js 9999999 times....

Thanks HOLLHOOK. You're right. Well, this is it...

I AM searching for a way to encapsulate a very time consuming operation (illustrating by sending out a value 9999999 times), like reading and writing into a buffer and manipulate the samples in a heavy computational math, all this without getting the patch to freeze.

There isn't much information about the Task object, so I'm bounded to make experiments by myself to figure this out by myself...

say for example that the code looks like this:

where the function big() is being called many times. Now what should I do to make it breath. In browsers (or in the max patcher itself which involves big loops) we have the ability to insert a delay between iterations so the processor would have time to do its other things.

But here we don't have that precious sleep() function.

My main question is how in general can I take a for loop or a while loop and turn it into a functional Task routine, no matter how heavy it is.

Thanks HOLLHOOK. You're right. Well,  this is it...
I AM searching for a way to encapsulate a very time consuming operation (illustrating by sending out a value 9999999 times), like reading and writing into a buffer and manipulate the samples in a heavy computational math, all this without getting the patch to freeze.

 There isn't much information about the Task object, so I'm bounded to make experiments by myself to figure this out by myself...

where the function  big() is being called many times. Now what should I do to make it breath. In browsers (or in the  max patcher itself which involves big loops) we have the ability to insert a delay between iterations so the processor would have time to do its other things.
But here we don't have that precious sleep() function.

My main question is how in general can I take a for loop or a while loop and turn it into a functional Task routine,  no matter how heavy it is.


Even calling an identity function withing the loop is' killing' the tasker.

I definitely blame my poor javascript skills...

Well scratch that.
Even calling an identity function withing the loop is' killing' the tasker.

What is going on here?
I definitely blame my poor javascript skills...


my prefered way to do long-running computations in js doesn't use the Task object.

For instance, if there is a function big, I'd rather call the next recursion of big() not directly in js, but instead call outlet("big", params_of_big); In max, connect the outlet of big with

[delay 0] - or deferlow, can't remember which one does the trick right now

That way max gets time to do what it has to do to keep the UI responsive.

my prefered way to do long-running computations in js doesn't use the Task object. 

For instance, if there is a function big, I'd rather call the next recursion of big() not directly in js, but instead call outlet("big", params_of_big); In max, connect the outlet of big with
[route big whatever_other_results]
[prepend big]
[delay 0] - or deferlow, can't remember which one does the trick right now
and connect it to the js inlet.

That way max gets time to do what it has to do to keep the UI responsive.


js Task object behavior under long procedural loop