PixiJS Texture.from Returns Destroyed Texture From Cache

Texture.from() checks PIXI.utils.TextureCache before creating a new texture, so a texture freed with destroy(true) can remain reachable through its URL or cacheId.

The goal is to determine whether destroy(true) automatically removes the corresponding TextureCache and BaseTextureCache entries, or whether the application must remove them manually to prevent stale reuse. PixiJS major versions handle cache invalidation differently, so behavior may vary across v6, v7, and v8 without version-specific confirmation.

• Does destroy(true) delete the global cache entry automatically?
• Which explicit cache-removal call prevents Texture.from() from returning a destroyed object?
• Does cache invalidation differ between PixiJS v6, v7, and v8?