Julien Bayle

Creating an array of LiveAPI objects, I'd like to know if objects are really killed if I splice all elements of that array.

It doesn't seem from a performance/efficiency point of view.

Indeed, my liveset is ok, no lag nothing.

I put the device, if I build a lot of callback, it lags a very bit (only the audio meters)

If I click on my button which splices ALL object in the array, it still lags.

If I delete the device, then undo, no more lags.

Creating an array of LiveAPI objects, I'd like to know if objects are really killed if I splice all elements of that array.
It doesn't seem from a performance/efficiency point of view.

Indeed, my liveset is ok, no lag nothing.
I put the device, if I build a lot of callback, it lags a very bit (only the audio meters)
If I click on my button which splices ALL object in the array, it still lags.
If I delete the device, then undo, no more lags.

are-liveapi-objects-instantiated-in-js-garbage-collected

I would imagine that a formal declaration of array to be null (as opposed to calling methods to remove objects from the patcher) might help.

I decide to activate this or that parameters to be listened (= create the corresponding LiveAPI object w/its callback)

It puts it inside the array at the index 3 for instance.

Then, I want to remove the object in 3 (= I don't want max to listen a specific parameter anymore)

Problem is:
I have an array with a length of n.

I decide to activate this or that parameters to be listened (= create the corresponding LiveAPI object w/its callback)
It puts it inside the array at the index 3 for instance.

I still think my suggestion is worth a try.

problem isn't the array but the objects which seem to remain in memory/cpu cycles or whatever.

problem isn't the array but the objects which seem to remain in memory/cpu cycles or whatever.
sounds strange.
first time I experiment that


Live API objects aren't going to get collected, I think. Id's are persistent, even if no longer assigned (I asked someone about this before, but perhaps something has changed since then). I don't know how this figures into memory management within js, though.

One thing you can do is remove the callback from the API by assigning the object.property = 0. This generally gets rid of any overhead I have. Just removing the js object's assignment does NOT remove the API object itself, afaik.

After rereading your post, I think that's what you are after: reassign the .property of the object to 0.

btw, assignment of the array to null will lead to api errors (or at least it used to, the last time I tried it).

Live API objects aren't going to get collected, I think.  Id's are persistent, even if no longer assigned (I asked someone about this before, but perhaps something has changed since then).  I don't know how this figures into memory management within js, though.

One thing you can do is remove the callback from the API by assigning the object.property = 0.  This generally gets rid of any overhead I have.  Just removing the js object's assignment does NOT remove the API object itself, afaik.

After rereading your post, I think that's what you are after:  reassign the .property of the object to 0.

btw, assignment of the array to null will lead to api errors (or at least it used to, the last time I tried it).


for sure, it only remove the reference and garbage collection can happen but of course doesn't free the placeof the LiveAPI objects.

removing the callback doesn't help a lot as far as I tested.

I asked to Andrew who probably answer here.

if you are interested by the purpose, you can check this :

http://julienbayle.net/2012/01/25/my-video-generator-global-architecture/

for sure, it only remove the reference and garbage collection can happen but of course doesn't free the placeof the LiveAPI objects.
removing the callback doesn't help a lot as far as I tested.

if you are interested by the purpose, you can check this :
http://julienbayle.net/2012/01/25/my-video-generator-global-architecture/


I know this is an old post but I'm actually having a similar issue. I am instantiating a lot of LiveAPI objects in my javascript code, and eventually it starts to lag my ableton set. The problem is that I am also using lots of observers as well (and also Task objects), so it is hard to narrow down the exact cause of the lag in the code so far. The only way to fix it is to delete the max plugin and then undo, as Julien mentioned in his original post. 

@JulienBayle, did you ever come up with a solution to the problem? Or does anyone else know?

I know this is an old post but I'm actually having a similar issue. I am instantiating a lot of LiveAPI objects in my javascript code, and eventually it starts to lag my ableton set. The problem is that I am also using lots of observers as well (and also Task objects), so it is hard to narrow down the exact cause of the lag in the code so far. The only way to fix it is to delete the max plugin and then undo, as Julien mentioned in his original post. 
@JulienBayle, did you ever come up with a solution to the problem? Or does anyone else know?

you could call this simple function i wrote.

It works well. To call after any "new LiveApi" instance

function DestroyLiveApiObject(t)
{
    t.property = '';
    t.id = 0;
    t = null;
}

@zack 
you could call this simple function i wrote.

It works well. To call after any "new LiveApi" instance

Are LiveAPI objects instantiated in JS garbage collected ?