Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory Leak on FtpTileService #4052

Open
Nursinghalo opened this issue Jan 16, 2024 · 0 comments
Open

Memory Leak on FtpTileService #4052

Nursinghalo opened this issue Jan 16, 2024 · 0 comments
Labels
Issue-Easy (good first issue) Beginners welcome! Issues with relative low difficulty. Issue-Task (low) This isn't a bug, but should be dealt with.

Comments

@Nursinghalo
Copy link

Nursinghalo commented Jan 16, 2024

HEAP ANALYSIS RESULT

1 APPLICATION LEAKS

References underlined with "~~~" are likely causes.
Learn more at https://squ.re/leaks.

3451 bytes retained by leaking objects
Signature: 216fbec4f783637e93619cffbd02a6ef2b
┬───
│ GC Root: Global variable in native code
│
├─ android.service.quicksettings.TileService$2 instance
│    Leaking: UNKNOWN
│    Retaining 4.0 kB in 19 objects
│    Anonymous subclass of android.service.quicksettings.IQSTileService$Stub
│    this$0 instance of com.amaze.filemanager.asynchronous.services.ftp.
│    FtpTileService
│    ↓ TileService$2.this$0
│                    ~~~~~~
╰→ com.amaze.filemanager.asynchronous.services.ftp.FtpTileService instance
​     Leaking: YES (ObjectWatcher was watching this because com.amaze.
​     filemanager.asynchronous.services.ftp.FtpTileService received
​     Service#onDestroy() callback and Service not held by ActivityThread)
​     Retaining 3.5 kB in 18 objects
​     key = 9e73288c-080f-4d3c-b17e-f80bce52e483
​     watchDurationMillis = 31009
​     retainedDurationMillis = 25966
​     mApplication instance of com.amaze.filemanager.application.AppConfig
​     mBase instance of android.app.ContextImpl
====================================
0 LIBRARY LEAKS

A Library Leak is a leak caused by a known bug in 3rd party code that you do
not have control over.
See https://square.github.
io/leakcanary/fundamentals-how-leakcanary-works/#4-categorizing-leaks
====================================
0 UNREACHABLE OBJECTS

An unreachable object is still in memory but LeakCanary could not find a strong
reference path
from GC roots.
====================================
METADATA

Please include this in bug reports and Stack Overflow questions.

Build.VERSION.SDK_INT: 29
Build.MANUFACTURER: TCL
LeakCanary version: 2.7
App process name: com.amaze.filemanager.debug
Stats: LruCache[maxSize=3000,hits=1742,misses=57054,hitRate=2%]
RandomAccess[bytes=2740323,reads=57054,travel=12300738144,range=14328589,size=18
443733]
Heap dump reason: user request
Analysis duration: 16620 ms
Heap dump file path: /storage/emulated/0/Download/leakcanary-com.amaze.
filemanager.debug/2024-01-15_22-56-52_411.hprof
Heap dump timestamp: 1705381032636
Heap dump duration: 3561 ms
====================================
@VishnuSanal VishnuSanal added Issue-Task (low) This isn't a bug, but should be dealt with. Issue-Easy (good first issue) Beginners welcome! Issues with relative low difficulty. labels Jan 16, 2024
@VishnuSanal VishnuSanal changed the title Leak Memory Leak on FtpTileService Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Easy (good first issue) Beginners welcome! Issues with relative low difficulty. Issue-Task (low) This isn't a bug, but should be dealt with.
Projects
None yet
Development

No branches or pull requests

3 participants