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
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
The text was updated successfully, but these errors were encountered:
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?
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
The text was updated successfully, but these errors were encountered: