Very slow/laggy search after long use
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- mobile-dev
Research direction
Start by locating the launcher's search feature and reproducing the slowdown after repeated searches on the affected app version. Investigate what changes as searches accumulate; the issue does not name files or tests. Done means repeated searches remain responsive, with the fix verified by a relevant test or a reproduction check.
Written by the indexing model from the issue text.
Description
Checklist
- I can reproduce the bug with the latest version given here.
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
- This issue contains only one bug.
- I have read and understood the contribution guidelines.
Affected app version
1.10.0
Affected Android/Custom ROM version
Android 11, MIUI 12.5.7
Affected device model
Xiaomi 21091116UG
How did you install the app?
GitHub releases
Steps to reproduce the bug
- Set the app as the default home screen.
- Use the app's search feature.
- After using the search feature for some time, the app becomes slow and unresponsive during subsequent searches.
Expected behavior
Search should not become slow and unresponsive.
Actual behavior
https://github.com/user-attachments/assets/f2ee8dc5-ba44-4dfd-ad4f-d976a3088874
Screenshots/Screen recordings
No response
Additional information
No response
- Dominant language
- Kotlin
- Stars
- 703
- Forks
- 85
- Avg merge
- 4d 39m
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from FossifyOrg/Launcher
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FossifyOrg/Launcher#453 ·
Maintainers usually reply within 3 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FossifyOrg/Launcher#447 ·
Maintainers usually reply within 3 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
FossifyOrg/Launcher#446 ·
Maintainers usually reply within 3 days
-
feature request needs triage
Difficulty 3/5 1-2 days Newbie friendliness 40/100
FossifyOrg/Launcher#461 ·
Maintainers usually reply within 3 days
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
FossifyOrg/Launcher#456 ·
Maintainers usually reply within 3 days
All issues in FossifyOrg/Launcher
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
ankidroid/Anki-Android#22408 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 Under an hour Newbie friendliness 72/100
afarber/OpenMapView#22 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nightscout/AndroidAPS#5245 ·
Maintainers usually reply within 1 day
-
Feature:Resolution
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
intellij-elixir/intellij-elixir#4396 ·
Maintainers usually reply within 1 day