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

[BUG] App is not responding during ~65mb / ~7k files tar file extraction #27

Closed
EleanorRigby76 opened this issue Feb 11, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@EleanorRigby76
Copy link

Describe the bug
When extracting NumPy's tar archive from pypi.org (~65mb archive with ~7k files) I encountered the app constantly erroring with Android's not responding pop-up. The extraction succeeded however the app's UI was unresponsive during extraction thus Android decided to constantly prompt me to either kill the app or wait, choosing wait allowed the extraction to continue.

To Reproduce
Steps to reproduce the behaviour:

  1. Attempt to extract a tar archive with a large amount of small files.
  2. Witness Android panic due to the app's UI not being responsive.
  3. Sit through countless app is not responding pop-ups having to click wait on every single one.

Expected behaviour
The app's UI should be responsive, or at least not trigger Android's built-in app not responding prompt.

Screenshots
IMG_20240211_124649
IMG_20240211_125403
IMG_20240211_125344

Smartphone (please complete the following information):

  • Device: Pixel 7
  • App version 4.3 from F-Droid
  • Android 13 / LineageOS 20 - LineageOS 20-20231229-NIGHTLY-panther

Additional context
From my limited understanding of Android app development this shouldn't happen if the extraction function is called asynchronously so that the UI is able to update even while the extraction is running. Kotlin docs on asynchronous programming are here.

@WirelessAlien WirelessAlien added the bug Something isn't working label Feb 14, 2024
@WirelessAlien WirelessAlien self-assigned this Feb 14, 2024
WirelessAlien added a commit that referenced this issue Feb 16, 2024
minor change
@WirelessAlien WirelessAlien reopened this Feb 16, 2024
@WirelessAlien
Copy link
Owner

I released a new version (just updated the code to do the job in background), let me know it is fixed or not. I will not close the issue now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants