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

Opening Downloads section or initiating a new download takes a long time when you have a lot of downloaded content #9672

Open
6 tasks done
jancborchardt opened this issue Jan 12, 2023 · 3 comments
Labels
bug Issue is related to a bug downloader Issue is related to the downloader GUI Issue is related to the graphical user interface

Comments

@jancborchardt
Copy link

Checklist

  • I am able to reproduce the bug with the latest version.
  • I made sure that there are no existing issues - open or closed - which I could contribute my information to.
  • I have read the FAQ 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 version

0.24.1

Steps to reproduce the bug

  1. Have a lot of Downloads already (100 or 200)
  2. Open the "Downloads" section via the sidebar (Alternatively try to initiate a download on a new video)
  3. Notice nothing is shown for a few seconds. The more existing downloads you have, the longer it takes to display
  4. At some point the list (or download dialog shows), along with a system modal "NewPipe isn’t responding". Just clicking "Wait" on there works so you can continue.

Expected behavior

  • Either the behavior could be the same as when you have not so many videos, in that it shows instantly (entries further down in the list can always be loaded in the background)
  • Or if that is difficult, a first step could be some loading feedback

Actual behavior

It takes several seconds without any feedback for the list content (or the download modal) to show up.

Screenshots/Screen recordings

No response

Logs

No response

Affected Android/Custom ROM version

Android 10 / LineageOS 17.1

Affected device model

Fairphone 3+

Additional information

No response

@jancborchardt jancborchardt added bug Issue is related to a bug needs triage Issue is not yet ready for PR authors to take up labels Jan 12, 2023
@opusforlife2 opusforlife2 added GUI Issue is related to the graphical user interface and removed needs triage Issue is not yet ready for PR authors to take up labels Jan 16, 2023
@Tibladar
Copy link

I have this issue with NewPipe 0.27.2 on Samsung Galaxy S21 Ultra.

NewPipe hangs after doing above steps to reproduce and the dialog "NewPipe isn't responding" is shown.
When clicking "Wait" the app can be used normally until the dialog comes back after a few seconds. This is now happens forever until you close and reopen NewPipe.

Scoop doesn't record a crash, even with the permission to read logs.
I attached a logcat with the relevant lines: logcat.zip
Input dispatching timed out (e1259e0 org.schabi.newpipe/org.schabi.newpipe.download.DownloadActivity (server) is not responding. Waited 10007ms for FocusEvent(hasFocus=true))

@Tibladar Tibladar mentioned this issue Jul 27, 2024
6 tasks
@ShareASmile ShareASmile added the downloader Issue is related to the downloader label Jul 27, 2024
@Foxite
Copy link

Foxite commented Aug 1, 2024

I'm also having this problem (Fairphone 4, lineageos for microg). It appears this can be fixed by clearing the download history (open sidebar, go to Downloads and clear history), it doesn't seem to be necessary to delete/move files out of the download folder.

Interestingly, if you have a lot of items in the download history, then it takes a lot of time to open the download history, and the same "not responding" bug happens after opening it. So it's probably related to that.

@jancborchardt
Copy link
Author

@Foxite thanks for the tip – so "Clear history" only clears that list, and doesn’t delete the files? That seems to be an ok workaround at least.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue is related to a bug downloader Issue is related to the downloader GUI Issue is related to the graphical user interface
Projects
None yet
Development

No branches or pull requests

5 participants