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

StorageAnalyzer slows system responsiveness after opening heavily populated media folders #1166

Open
dgw opened this issue May 9, 2024 · 0 comments
Labels
bug Something isn't working as expected triage This ticket needs to be sorted and labeled.

Comments

@dgw
Copy link

dgw commented May 9, 2024

Describe the bug
System becomes slow or unresponsive after StorageAnalyzer has been used to view a folder containing many (thousands) media files.

To Reproduce
Steps to reproduce the behavior:

  1. Place 5-10 thousand (or more) media files into a single folder, e.g. /storage/emulated/0/Pictures/TestFolder
    • Optionally add a .nomedia file to this folder — I am not sure yet if this influences the behavior
  2. Scan device with StorageAnalyzer
  3. Browse the StorageAnalyzer results; system responsiveness should still be normal
  4. Enter the test folder containing thousands of media files
  5. Scrolling may or may not work; SD Maid SE should now be slow to react to Back button presses or other input
  6. When I have been able to get StorageAnalyzer to back out of the problematic folder, system responsiveness has not recovered, as if some background task(s) spawned by opening the folder stay(s) running

Expected behavior
Regardless of how many files are in a given folder, browsing StorageAnalyzer results should remain responsive.

Smartphone (please complete the following information):

  • Device: ASUS ROG Phone 3 and OnePlus Pad
  • OS: Android 12 and OxygenOS 14 (yes, it's just skinned Android)
  • Root status: No
  • SD Maid 2/SE version: 0.24.0-beta0

Debug log
I will be happy to add this later, if needed; it takes quite a while to scan my devices

Screenshots/Video
As above, happy to add if needed.

Additional context
Generally I end up restarting the whole device to get responsiveness back. I can usually do so through the normal menus, with patience, but occasionally it has been bad enough that I considered just holding the power button to force shutdown.

@dgw dgw added bug Something isn't working as expected triage This ticket needs to be sorted and labeled. labels May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as expected triage This ticket needs to be sorted and labeled.
Projects
None yet
Development

No branches or pull requests

1 participant