You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All js class bindings come with a free() method, which frees up the memory allocated for them when they are instantiated, let's say there is a loop on js which inside that class binding is instantiated, does some other stuff and just then WITHOUT calling free() we go to next iteration, would this cause memory leak and those instances on each iteration persist on memory?
or would they automatically end up in js gc and go out of scope themselves?
for(;;){constbindingClassInstance=newBindingClass();// do something and NOT call free() on above instance}
The text was updated successfully, but these errors were encountered:
Summary
All js class bindings come with a
free()
method, which frees up the memory allocated for them when they are instantiated, let's say there is a loop on js which inside that class binding is instantiated, does some other stuff and just then WITHOUT calling free() we go to next iteration, would this cause memory leak and those instances on each iteration persist on memory?or would they automatically end up in js gc and go out of scope themselves?
The text was updated successfully, but these errors were encountered: