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
The behaviour described above should be fixed to avoid duplication of workers, unless of course it was not intended that way, which I have my doubts.
it would be nice to have web workers clean up when app destroy is called, right now I don't see code for that.
Steps to Reproduce
In our case, the duplicate appears after the whole application has been remounted. Unfortunately I can't create a playground, but I hope even so the essence of the problem will be visible and clear.
Environment
pixi.js version: 8.1.6
Browser & Version: Chrome 125
OS & Version: MacOS Sonoma
Running Example:
Possible Solution
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Current Behavior
I noticed that every time a created worker sends a message, pixi push it to the worker's pool, which leads to duplicate workers in memory.
pixijs/src/assets/loader/workers/WorkerManager.ts
Line 91 in cde22b1
Expected Behavior
The behaviour described above should be fixed to avoid duplication of workers, unless of course it was not intended that way, which I have my doubts.
Steps to Reproduce
In our case, the duplicate appears after the whole application has been remounted. Unfortunately I can't create a playground, but I hope even so the essence of the problem will be visible and clear.
Environment
pixi.js
version: 8.1.6Possible Solution
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: