nextcloud / nextcloud/talk-android
EglRenderer not closed properly
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 739
- Forks
- 321
- Avg merge
- 14h 59m
- Merged PRs (30d)
- 151
Description
Steps to reproduce (not yet sure if it only happens for some scenarios)
- start a call
- leave the call
Expected behaviour
EglRenderer must be closed properly.
This should look like here: https://github.com/flutter-webrtc/flutter-webrtc/issues/126#issuecomment-696378447
Actual behaviour
the logcat shows multiple entries of:
EglRenderer: surface_viewDuration: 4038 ms. Frames received: 0. Dropped: 0. Rendered: 0. Render fps: ,0. Average render time: NA. Average swapBuffer time: NA.
this might lead to memory problems?!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by starting and leaving a call, then inspect logcat for repeated EglRenderer entries. Trace the renderer lifecycle through the Android call and rendering code, and compare the expected closure behavior with the linked Flutter WebRTC issue. Done means the renderer is closed after leaving a call and the repeated log entries no longer appear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- audio-video-rtc, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100