Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Canvas] different JS behavior for canvas & context destruction #810

Closed
CedricGuillemet opened this issue Jun 22, 2021 · 4 comments
Closed
Assignees
Milestone

Comments

@CedricGuillemet
Copy link
Contributor

With JSC and Chakra, canvas and context are destroyed just after the dynamicTexture is disposed.
With V8, those 2 objects are not destroyed before the JS Runtime is destroyed. More and more rendertargets are created and kept in memory. After a while, bgfx can't create a new one.

@CedricGuillemet
Copy link
Contributor Author

@thomlucc thomlucc added the 6.0 label Sep 23, 2022
@thomlucc thomlucc modified the milestones: Future, 6.0 Sep 23, 2022
@thomlucc thomlucc removed the 6.0 label Sep 23, 2022
@bghgary bghgary self-assigned this Oct 13, 2022
@bghgary
Copy link
Contributor

bghgary commented Oct 13, 2022

Look at this with the shutdown scenarios.

@CedricGuillemet
Copy link
Contributor Author

Issue can be mitigated by increasing the number of FrameBuffer. With a number big enough (4096+), Framebuffer are destroyed at some point. Setting it to 256 for now in the CI.

@CedricGuillemet
Copy link
Contributor Author

CedricGuillemet commented Sep 11, 2023

Change done in this PR : #1260
Closing for now. reopen if a better solution is needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants