Bug 405306 - logcat: ActivityThread: Service org.kde.kdeconnect.BackgroundService has leaked IntentReceiver
Summary: logcat: ActivityThread: Service org.kde.kdeconnect.BackgroundService has leak...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdeconnect
Classification: Applications
Component: android-application (other bugs)
Version First Reported In: unspecified
Platform: Android Android 9.x
: NOR minor
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-10 11:51 UTC by Christian Stadelmann
Modified: 2025-07-11 03:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Stadelmann 2019-03-10 11:51:06 UTC
SUMMARY
According to `adb logcat`, KDE connect is leaking `IntentReceiver`

STEPS TO REPRODUCE
unclear. Enable USB debugging on your Android smartphone and run `adb logcat`, then have a look at the logs.

OBSERVED RESULT
ActivityThread: Service org.kde.kdeconnect.BackgroundService has leaked IntentReceiver org.kde.kdeconnect.KdeConnectBroadcastReceiver@e55664a that was originally registered here. Are you missing a call to unregisterReceiver()?
ActivityThread: android.app.IntentReceiverLeaked: Service org.kde.kdeconnect.BackgroundService has leaked IntentReceiver org.kde.kdeconnect.KdeConnectBroadcastReceiver@e55664a that was originally registered here. Are you missing a call to unregisterReceiver()?
ActivityThread: 	at android.app.LoadedApk$ReceiverDispatcher.<init>(LoadedApk.java:1429)
ActivityThread: 	at android.app.LoadedApk.getReceiverDispatcher(LoadedApk.java:1210)
ActivityThread: 	at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1488)
ActivityThread: 	at android.app.ContextImpl.registerReceiver(ContextImpl.java:1461)
ActivityThread: 	at android.app.ContextImpl.registerReceiver(ContextImpl.java:1449)
ActivityThread: 	at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:623)
ActivityThread: 	at org.kde.kdeconnect.BackgroundService.onCreate(BackgroundService.java:284)
ActivityThread: 	at android.app.ActivityThread.handleCreateService(ActivityThread.java:3559)
ActivityThread: 	at android.app.ActivityThread.access$1300(ActivityThread.java:202)
ActivityThread: 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1681)
ActivityThread: 	at android.os.Handler.dispatchMessage(Handler.java:107)
ActivityThread: 	at android.os.Looper.loop(Looper.java:198)
ActivityThread: 	at android.app.ActivityThread.main(ActivityThread.java:6729)
ActivityThread: 	at java.lang.reflect.Method.invoke(Native Method)
ActivityThread: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
ActivityThread: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)

EXPECTED RESULT
No error log entry

SOFTWARE/OS VERSIONS
Android 9, security patch level 2019-02-01
Hardware: Nokia 5 (HMD Global TA-1053)
KDE connect: version 1.11 installed from f-droid store
Comment 1 aristsakas 2025-06-11 22:39:50 UTC
Thank you for the bug report, and I'm sorry we didn't manage to get to it before. KDE Connect depends on the specifics of the device and network configuration. We recommend that you first try the troubleshooting steps at https://userbase.kde.org/KDEConnect#Troubleshooting, and if these do not work, try asking at discuss.kde.org or your distibution's support forums. Bug reports are only actionable for developers if the cause can be clearly identified and is something that can be fixed on our end, and at those places you can get help with narrowing this down and making it actionable for developers.
I am closing this bug report, but please do not hesitate to file a new one if you can narrow down the issue to a particular cause that can be fixed in KDE Connect.
KDEConnect - KDE UserBase Wiki
Comment 2 Bug Janitor Service 2025-06-26 03:47:59 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2025-07-11 03:47:44 UTC
๐Ÿ›๐Ÿงน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.