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
{{ message }}
This repository was archived by the owner on May 12, 2026. It is now read-only.
Support for pooling would be great. This kind of feautre is must have for html5 games to prevent GarbageCollector throttling effect aka lagging.
The only file that manage memory is in resize.js?
We should then provide callbacks or methods like: onCreateBuffer() and onUtilizeBuffer() that would be called in resize method
in default behaviour onUtilizeBuffer will be just empty, but if someone will be in need both can be overridden to obtain Buffer from Pool and release Buffer to pool.
I can do the code for it but need to be sure that managing memory is only about resize.js source.
Support for pooling would be great. This kind of feautre is must have for html5 games to prevent GarbageCollector throttling effect aka lagging.
The only file that manage memory is in resize.js?
We should then provide callbacks or methods like:
onCreateBuffer()andonUtilizeBuffer()that would be called in resize methodin default behaviour onUtilizeBuffer will be just empty, but if someone will be in need both can be overridden to obtain Buffer from Pool and release Buffer to pool.
I can do the code for it but need to be sure that managing memory is only about resize.js source.