nextcloud / nextcloud/talk-android

A resource failed to call close

Open
#2,983 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug
Dominant language
Kotlin
Stars
739
Forks
321
Avg merge
14h 59m
Merged PRs (30d)
151

Description

while running the app following message occured (soon after startup). No crash or other impact was recognized yet.

2023-04-28 09:20:56.020  6756-6892  okhttp.OkHttpClient     com.nextcloud.talk2                  I  Upgrade: websocket
2023-04-28 09:20:56.020  6756-6892  okhttp.OkHttpClient     com.nextcloud.talk2                  I  Sec-WebSocket-Accept: Hh1rL0Hc0UMGS75hi2THkByX1Lw=
2023-04-28 09:20:56.021  6756-6892  okhttp.OkHttpClient     com.nextcloud.talk2                  I  <-- END HTTP
2023-04-28 09:20:56.037  6756-6892  WebSocketInstance       com.nextcloud.talk2                  D  Receiving : okhttp3.internal.ws.RealWebSocket@ea7b78c {"type":"welcome","welcome":{"version":"1.1.0-1~ubuntu22.04","features":["audio-video-permissions","hello-v2","incall-all","mcu","simulcast","switchto","transient-data","update-sdp","virtual-sessions","welcome"]}}
2023-04-28 09:20:56.125  6756-6892  WebSocketInstance       com.nextcloud.talk2                  D  Receiving : okhttp3.internal.ws.RealWebSocket@ea7b78c {"type":"hello","hello":{"version":"1.0","sessionid":"KhsFNJdW33-_D6_gsRiDdfYfmlUv6Xhl6q0bRmnCFwx8VHpNWEJuRXdfMXB3ZWFTV3ctZHZhZFRCZzVKdjQ3alE1WEhWSjVlSV9oNUo0WkZZbGM2bjR5RlJtQl9Fc2NNSWVNbmRmTkptZVdHRlJoRExLdU5VQnVnTzdXcE1yUERRT185dW1YVFZzclMtLXlTY1hzWDMzR21DUTE1d2E5NHJmN0NkSzFWU3doYXJYdmE4QmxxZlBQM3ZxQkYwVVRQeG1kVUVjZlVjYXdjV3w2NTQ2NjYyODYx","resumeid":"MTY4MjY2NjQ1NnxQM0w2WUZyZG9rbVc1R0V6dzJESXV3R2hsNjRTRS1LUHB2WThMY3JCZDdqanJ2VGdlSGV1ZS0yYWF3X2RXTkNxVjR5RUxZQ0MySFJXWnhMMUxDMi1kQVZUdXpSb0FCbTVyNmNqY2N0VEZHYUlEOXY2T2EyemRjM2NOMUhzeWhFRkRLeGRIZ1FVVk9XcFFMZnF1M0lUMXJuaUpYemdDclVRWXRQSW5hTVJyQmRIfGbS0ME8Vw6pKJvzxaBYM3rgOU7Po0hZhMmSf10WhBvr","userid":"marcel2","server":{"version":"1.1.0-1~ubuntu22.04","features":["audio-video-permissions","hello-v2","incall-all","mcu","simulcast","switchto","transient-data","update-sdp","welcome"]}}}
2023-04-28 09:20:56.135  6756-6892  EventBus                com.nextcloud.talk2                  D  No subscribers registered for event class com.nextcloud.talk.events.WebSocketCommunicationEvent
2023-04-28 09:20:56.136  6756-6892  EventBus                com.nextcloud.talk2                  D  No subscribers registered for event class org.greenrobot.eventbus.NoSubscriberEvent
2023-04-28 09:20:58.743  6756-6910  ProfileInstaller        com.nextcloud.talk2                  D  Installing profile for com.nextcloud.talk2
2023-04-28 09:20:59.214  6756-6767  nextcloud.talk2         com.nextcloud.talk2                  I  Background concurrent copying GC freed 255608(16MB) AllocSpace objects, 34(1000KB) LOS objects, 49% free, 19MB/39MB, paused 398us,180us total 245.875ms
2023-04-28 09:20:59.224  6756-6770  System                  com.nextcloud.talk2                  W  A resource failed to call close. 
Nextcloud Talk app version

16.1.0 Alpha 08

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the warning from the provided Android log on Nextcloud Talk 16.1.0 Alpha 08 and identify which resource emits “A resource failed to call close.” Trace that resource to the relevant app entry point; done means the warning no longer appears during the reported startup flow without introducing a crash or other impact.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.