nextcloud / nextcloud/talk-android
Crash in call with around 40 participants
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 739
- Forks
- 321
- Avg merge
- 14h 59m
- Merged PRs (30d)
- 151
Description
Steps to reproduce
- Try to connect with Nextcloud Talk app to the Nextcloud Internal Company Call (around 40 participants I think)
Expected behaviour
Listen to people in the call
Actual behaviour
Heard for a minute some robo voice. After a minute the app decided to crash.
Device information
Device: LG G4
Android version: 9
Talk version: 11.1.0
Server information
Nextcloud version: cloud.nextcloud.com
Talk version: Don't know
Custom Signaling server configured: Don't know
Custom TURN server configured: Don't know
Custom STUN server configured: Don't know
Server log (data/nextcloud.log)
Don't have them
I know there are not many information in the bug report. Probably my phone can't just handle the load. Let me know if I can provide additional information.
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
No source files, tests, crash logs, or specific entry points are named. Start by reproducing the issue on the stated LG G4 and Android 9 setup with a call of around 40 participants, collect Android crash logs and relevant server details, and use them to locate the failing call path. Done means the crash and reported robo voice are reproduced, diagnosed, and covered by an appropriate verification.
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