Adam Murray

I have a patch with 398 pattr objects in it. It's too big to post, but it's quite easy to create this number of pattrs by using a poly~ inside a poly~.

I need to do some complicated state management and would like to use javascript. But first I need to make my script aware of all the pattr objects. So I'm sending getclientlist to pattrstorage and routing that to my javascript via [route clientlist]

The problem is, inside the javascript a few clientlist messages randomly arrive AFTER the done message! This prevents me from building the list properly.

        post(messagename + "n")        

        post("done, count = " + count + "n")

The count varies between about 390 and 398. It is very rarely the full 398.

In my max patch I can do something like this and the value is correct every time (and "done" always arrives last if I print out the client list).

I just noticed this only seems to happen when overdrive is enabled. Unfortunately I need overdrive on or my patch does not work correctly. So... what's going on here? I thought overdrive was supposed to make event timing better? I guess the messages arrive faster than the js can process it so some get deferred by the scheduler.

As I finished describing this problem, I realized a solution:

If anyone else is making patches with hundreds of pattrs, [deferlow] is your best friend. It has also fixed most of my patch's initialization problems (almost every loadbang is firing before the pattrs are ready).

But these weird timing issues are getting scary, I don't know what else is going to randomly malfunction. Maybe I need to see if I can avoid overdrive...

I have a patch with 398 pattr objects in it. It's too big to post, but it's quite easy to create this number of pattrs by using a poly~ inside a poly~. 

function anything() {
	if(messagename != "done") {
		post(messagename + "n")		
		count++
	}
	else {
		post("done, count = " + count + "n")
		count = 0
	}
}

If anyone else is making patches with hundreds of pattrs, [deferlow] is your best friend. It has also fixed most of my patch's initialization problems (almost every loadbang is firing before the pattrs are ready). 

But these weird timing issues are getting scary, I don't know what else is going to randomly malfunction. Maybe I need to see if I can avoid overdrive...


bug-javascript-cant-handle-large-pattrstorage-clientlist-when-overdrive-is-enabled

On 25 Mar 2008, at 06:53, Adam Murray wrote:

> I guess the messages arrive faster than the js can process it so 

As I recall, by default, everything in JS runs outside overdrive 

(i.e. deferred). There are facilities to run high-priority threads, 

but I had stability problems when I tried doing that (a year or so ago).

nick rothwell -- composition, systems, performance -- 

> I guess the messages arrive faster than the js can process it so  
> some get deferred by the scheduler.

As I recall, by default, everything in JS runs outside overdrive  
(i.e. deferred). There are facilities to run high-priority threads,  
but I had stability problems when I tried doing that (a year or so ago).

   nick rothwell -- composition, systems, performance -- http:// 
www.cassiel.com


Quote: nick rothwell / cassiel wrote on Tue, 25 March 2008 01:43

----------------------------------------------------

> As I recall, by default, everything in JS runs outside overdrive 

If that's the case, why are some messages arriving out of order? Shouldn't they all get deferred in the same order?

Quote: nick rothwell / cassiel wrote on Tue, 25 March 2008 01:43
----------------------------------------------------
>
> As I recall, by default, everything in JS runs outside overdrive  
> (i.e. deferred). 

If that's the case, why are some messages arriving out of order? Shouldn't they all get deferred in the same order?


the solution was to set the immediate property

i think that this is a bug not a feature !

i had the same problem.
the solution was to set the immediate property
for the function: 

i think that this is a bug not a feature !


Quote: videomasta wrote on Sat, 12 April 2008 07:11

> the solution was to set the immediate property

Quote: videomasta wrote on Sat, 12 April 2008 07:11
----------------------------------------------------
> i had the same problem.
> the solution was to set the immediate property
> for the function: 
>
> in your case:
>
> anything.immediate = 1;

BUG: javascript can't handle large pattrstorage clientlist when overdrive is enabled