CityLights Posted June 15, 2021 Share Posted June 15, 2021 Should destroying filters be part of my memory management strategy? I noticed that these filters inherit a `destroy` method from `PIXI.Shader. Should I be destroying filter instances if I know they will no longer be used? Quote Link to comment Share on other sites More sharing options...
ivan.popelyshev Posted June 15, 2021 Share Posted June 15, 2021 No, it doesnt matter. Shader program itself is never freed in pixi CityLights 1 Quote Link to comment Share on other sites More sharing options...
CityLights Posted June 15, 2021 Author Share Posted June 15, 2021 (edited) 24 minutes ago, ivan.popelyshev said: No, it doesnt matter. Shader program itself is never freed in pixi Perhaps some clarification can be added to the docs, explaining that it is not necessary to call the inherited `destroy` method. I was also getting some weird errors after destroying an instance of`OutlineFilter`. Thanks for your help. Edited June 15, 2021 by CityLights Quote Link to comment Share on other sites More sharing options...
ivan.popelyshev Posted June 16, 2021 Share Posted June 16, 2021 > I was also getting some weird errors after destroying an instance of`OutlineFilter`. that's strange Quote Link to comment Share on other sites More sharing options...
a-c-sreedhar-reddy Posted July 2, 2021 Share Posted July 2, 2021 Hi @ivan.popelyshev Where would pixi.filters destroy be useful? Quote Link to comment Share on other sites More sharing options...
ivan.popelyshev Posted July 2, 2021 Share Posted July 2, 2021 I dont know such cases Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.