TeamAmaze / TeamAmaze/AmazeFileManager
OutOfMemoryError when due to stopped seach that seems to still be running in the background
Open
Nobody has claimed this yet.
Area-Search
Issue-Bug
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Reproduice
- explore as root
- go to
/data/data - search for something
- after few seconds, renounce and tap the middle of the screen the dismiss the search
- wait or go navigate in another more "normal" folder, like Download
- crash
Context
- version 3.2.2 from F-Droid
- Phone: Nexus 5
- Android 7.1.2 (LineageOS for microG 14.1)
logs
logcat-browsing-data-data-reproduiced.txt
Is it normal that there is so much recursion of SearchAsyncTask.search ?
Has /data/data for much depth? Or is the recursion for something else.?
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 with the attached logcat and the SearchAsyncTask.search entry point, reproducing the search under /data/data and stopping it as described. Trace whether the stopped search continues running or recurses until the OutOfMemoryError, then verify that dismissing the search no longer crashes while navigating to another folder.
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
- Mostly clear
- Newbie friendliness
- 30/100