nextcloud / nextcloud/talk-android
app crash while in call
Open
Nobody has claimed this yet.
1. to develop
bug
feature: call ☎️
- Dominant language
- Kotlin
- Stars
- 739
- Forks
- 321
- Avg merge
- 14h 59m
- Merged PRs (30d)
- 151
Description
Steps to reproduce
- join call
- used sermo, so with hpb
- tested on redmi note 7
- stay in call for a while
Expected behaviour
no crash
Actual behaviour
app suddenly crashed. error:
2022-10-13 15:05:22.960 19497-20390 org.webrtc.Logging com.nextcloud.talk2 I EglRenderer: surface_viewDropping frame - No surface
2022-10-13 15:05:22.961 19497-20269 org.webrtc.Logging com.nextcloud.talk2 I EglRenderer: surface_viewDropping frame - No surface
2022-10-13 15:05:22.962 19497-20462 org.webrtc.Logging com.nextcloud.talk2 I EglRenderer: surface_viewDropping frame - No surface
2022-10-13 15:05:22.962 19497-20397 org.webrtc.Logging com.nextcloud.talk2 I EglRenderer: surface_viewDropping frame - No surface
2022-10-13 15:05:22.962 19497-20380 org.webrtc.Logging com.nextcloud.talk2 I EglRenderer: surface_viewDropping frame - No surface
2022-10-13 15:05:22.962 19497-20473 org.webrtc.Logging com.nextcloud.talk2 I EglRenderer: surface_viewDropping frame - No surface
2022-10-13 15:05:22.962 19497-20254 org.webrtc.Logging com.nextcloud.talk2 I EglRenderer: surface_viewDropping frame - No surface
2022-10-13 15:05:22.967 19497-19510 nextcloud.talk com.nextcloud.talk2 I Background concurrent copying GC freed 282527(12MB) AllocSpace objects, 0(0B) LOS objects, 49% free, 12MB/25MB, paused 466us total 207.028ms
2022-10-13 15:05:22.971 19497-19512 System com.nextcloud.talk2 E Uncaught exception thrown by finalizer
2022-10-13 15:05:22.973 19497-19512 System com.nextcloud.talk2 E java.lang.NullPointerException: Attempt to do a synchronize operation on a null object
at android.view.Surface.release(Surface.java:254)
at android.view.Surface.finalize(Surface.java:242)
at java.lang.Daemons$FinalizerDaemon.doFinalize(Daemons.java:291)
at java.lang.Daemons$FinalizerDaemon.runInternal(Daemons.java:278)
at java.lang.Daemons$Daemon.run(Daemons.java:139)
at java.lang.Thread.run(Thread.java:919)
2022-10-13 15:05:22.992 19497-20390 org.webrtc.Logging com.nextcloud.talk2 I EglRenderer: surface_viewDropping frame - No surface
2022-10-13 15:05:22.993 19497-20269 org.webrtc.Logging com.nextcloud.talk2 I EglRenderer: surface_viewDropping frame - No surface
2022-10-13 15:05:22.993 19497-20473 org.webrtc.Logging com.nextcloud.talk2 I EglRenderer: surface_viewDropping frame - No surface
2022-10-13 15:05:22.993 19497-20397 org.webrtc.Logging com.nextcloud.talk2 I EglRenderer: surface_viewDropping frame - No surface
2022-10-13 15:05:22.993 19497-20380 org.webrtc.Logging com.nextcloud.talk2 I EglRenderer: surface_viewDropping frame - No surface
2022-10-13 15:05:22.993 19497-20237 org.webrtc.Logging com.nextcloud.talk2 I EglRenderer: surface_viewDropping frame - No surface
Device brand and model
redmi note 7
Android version
10
Nextcloud Talk app version
15.1.0 Alpha 05
Nextcloud server version
No response
Talk version
No response
Custom Signaling server configured
No response
Custom TURN server configured
No response
Custom STUN server configured
No response
Android logs
No response
Server log
No response
Additional information
No response
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
Start by reproducing the crash during a call on a Redmi Note 7 running Android 10, using the reported WebRTC EglRenderer and Surface finalizer logs as the first evidence. Investigate the call and surface lifecycle around the reported java.lang.NullPointerException; done means the app no longer crashes after remaining in a call for a while.
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
- 25/100