Since OWT 5.0: Screen capturer crashes in onFrame
dilldilldill opened this issue · 7 comments
W/System.err: java.lang.IllegalStateException: release() called on an object with refcount < 1
W/System.err: at org.webrtc.RefCountDelegate.release(RefCountDelegate.java:42)
W/System.err: at org.webrtc.TextureBufferImpl.release(TextureBufferImpl.java:125)
W/System.err: at org.webrtc.VideoFrame.release(VideoFrame.java:188)
W/System.err: at org.webrtc.VideoSource$1.onFrameCaptured(VideoSource.java:77)
W/System.err: at org.webrtc.ScreenCapturerAndroid.onFrame(ScreenCapturerAndroid.java:200)
W/System.err: at org.webrtc.SurfaceTextureHelper.tryDeliverTextureFrame(SurfaceTextureHelper.java:374)
W/System.err: at org.webrtc.SurfaceTextureHelper.lambda$new$0$SurfaceTextureHelper(SurfaceTextureHelper.java:207)
W/System.err: at org.webrtc.-$$Lambda$SurfaceTextureHelper$073Iq_oVBecUTQR2U0VmYQ8_7lM.onFrameAvailable(Unknown Source:2)
W/System.err: at android.graphics.SurfaceTexture$1.handleMessage(SurfaceTexture.java:211)
W/System.err: at android.os.Handler.dispatchMessage(Handler.java:106)
W/System.err: at android.os.Looper.loop(Looper.java:233)
W/System.err: at android.os.HandlerThread.run(HandlerThread.java:67
As I updated my the OWT android client to the newest 5.0 release the very simple OwtScreenCapturer fails with the above IllegalStateException. As the code I am using seems trivial and this problem was introduced when I updated OWT to 5.0 I tend to believe, that the problem is somewhere in the SurfaceTextureHelper maybe? I tried to look into the code but couldn't find anything obvious. The fact that I can not find any one on the internet having the same problem leaves me a little unconfident. Any ideas any one?
Same here! Did you solve it yet?
Same here! Did you solve it yet?
Unfortunately not.
That's sad. It is a big blocker for us.
@jianjunz @zhangyihui1 do you guys have an idea?
@dilldilldill did you find a solution? Unfortunately, the owt people don't care...
@dilldilldill did you find a solution? Unfortunately, the owt people don't care...
Not yet, still checking the repo daily, waiting for a fix
No one?
👉👈
nope... not fixed yet... weird issue, no support... :(