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
Solidjs has powerful reactive performance and is fit to be a general framework for some canvas UI lib such as UI in pixijs.
However when I'm intergrating the solidjs into pixijs, I found that the solidjs custom renderer just create a node and do not call some destroy functions when it's no longer needed.
Thus some resource wouldn't auto free (yoga-layout node's calculating resource, etc.) and cause memory leak.
Could the custom renderer add a destroyNode() function to help with the resouce lifecycle managing? I know that as the creating action is invoked in a component so the destroy action to be done in the same component lifecycle too is resaonable and the 'usexxx' api can handle this, but an intergated and simple attribute is also helpful.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Solidjs has powerful reactive performance and is fit to be a general framework for some canvas UI lib such as UI in pixijs.
However when I'm intergrating the solidjs into pixijs, I found that the solidjs custom renderer just create a node and do not call some destroy functions when it's no longer needed.
Thus some resource wouldn't auto free (yoga-layout node's calculating resource, etc.) and cause memory leak.
Could the custom renderer add a destroyNode() function to help with the resouce lifecycle managing? I know that as the creating action is invoked in a component so the destroy action to be done in the same component lifecycle too is resaonable and the 'usexxx' api can handle this, but an intergated and simple attribute is also helpful.
Beta Was this translation helpful? Give feedback.
All reactions