This repository was archived by the owner on Jul 22, 2024. It is now read-only.
Fix leaked JNI local reference in GeckoSurfaceTexture#2772
Merged
Conversation
MortimerGoro
changed the title
bluemarvin
reviewed
Feb 10, 2020
Comment on lines
162
to
+163
| surface = GeckoSurfaceTexture::Create(aSurfaceHandle); | ||
| m.surfaceMap[aSurfaceHandle] = surface; |
Contributor
There was a problem hiding this comment.
What condition causes us to have a aSurfaceHandle value with out it being in the m.surfaceMap?
Contributor
Author
There was a problem hiding this comment.
A new texture that hasn't been used before or StopPresenting() call which cleared the surfaces
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I hit a JNI reference overflow when working on exit from WebXR. This happens because exit is not working yet and the ExternalBlitter->cancelFrame() is called every frame, leading to a crash after some seconds.
The leak also happens in WebVR but in a slower pace