PIXI.Texture.EMPTY gets destroyed

[colourclash]

Hi,
This may not be a typical use case, but in my project I have some sprites which are created without a texture (in a sprite pool) and later on, those sprites may get destroyed.
The side effect I experienced, is that the PIXI.Texture.EMPTY property is also destroyed.
This will reproduce the problem:

var s = new PIXI.Sprite();
this.addChild(s);
s.destroy(true);
this.addChild(new PIXI.Sprite()); //rte :(

It's easy enough to work around the problem by checking whether the sprite has a texture before destroying it, but I thought I'd write this down in case anyone else gets tripped up by it!

[ivan.popelyshev]

Nice bug =)

[GBear]

is this fixed?

[xerver]

4 hours ago, GBear said:

is this fixed?

No: https://github.com/pixijs/pixi.js/issues/2460

[ivan.popelyshev]

Its in dev, but in v4, not v3. You can modify your v3 accordingly. https://github.com/pixijs/pixi.js/pull/2464