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

CapturerObserver.onFrame leaks native memory in libjingle_peerconnection_so.so #97

Open
StingEmperor opened this issue Jan 16, 2024 · 2 comments

Comments

@StingEmperor
Copy link

StingEmperor commented Jan 16, 2024

We created a capturer class very similar to ScreenCapturerAndroid, that uses DisplayManager over the media projection api. However, I have found that calling CapturerObserver.onFrameCaptured creates a memory leak that Android studio profiler blames on libjingle_peerconnection_so.so.

If I simply comment out the CapturerObserver.onFrameCaptured step, my video track is now broken but the memory leak is gone.

I can provide screenshots, more info, etc, upon request. tried with version 1.1.1 and 1.1.0

@StingEmperor
Copy link
Author

the title should be "CapturerObserver.onFrameCaptured leaks native memory in libjingle_peerconnection_so.so" sorry

@StingEmperor
Copy link
Author

i traced it back to HardwareVideoEncoder.deliverEncodedImage, if i just comment out the call to deliverEncodedImage i don't get the leak in the profiler... @skydoves can we get this looked into?

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

No branches or pull requests

1 participant