-
-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
[aria2c] Sometimes the download suddenly stops responding #5931
Comments
cc @Lesmiscore |
TL;DR: I'd say to avoid aria2c all the time, at least for yt-dlp. It's not your superhero. If you still want to use, use aria2c is particularly weird and unstable downloader amongst the all others - it sometimes stuck without explaining why, or even it can't download those that works 100% with native downloader. Honestly, I don't want to "fight" aria2c to dig in its behavior. Author doesn't know about functionalities of HTTP servers1, they don't give any response for Socks5 support request2 and leading/trailing spaces are automagically removed... Fighting aria2c is an insane work, anyway. There is no wonder even if it starts strike while being accessed via RPC... because it's aria2c. Aria2c is unstable most of the time. @pukkandan I regret I can't say that because the changes were suddenly made, but it should be enabled by user, instead of by default. Thoughts? Footnotes
|
I'd argue this is still something that should be fixed or disabled by default in yt-dlp. I've rarely had problems with aria2c in the past, but this new update without the compat options constantly keeps getting stuck. That being said, if what @Lesmiscore is saying is true, imo the README should mention that aria2c shouldn't be used. At the moment it seems to imply that setting it is a good thing. |
After a number of requests, the RPC simply stops responding. The only reference for this I could find is aria2/aria2#515. The issue isn't even limited to fragmented downloads, but happens for any large file. For now, the only solution I can see is to revert the progress reporting feature |
Can't |
If we could timeout the RPC call, the the feature could be salvaged. But the issue is happening in a way that doesn't obey |
Check aria2p listener, it's working well. Never missed any completed download. He using websocket with variable timeout. |
hello @pukkandan , i get stuck at 100% when have
it should end line as below
|
Upstream a similar thing has been implemented using aria2p but maybe no-one has used it hard enough to provoke a similar problem. |
DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE
Checklist
Provide a description that is worded well enough to be understood
Sometimes the downloads suddenly stop responding, sometimes at ~80%, ~90%, when this happens I have to end the process and start it again to complete the download.
After a few hours of downloading random content and witnessing these behaviors, I found a URL that always stops at 100%, the download never completes. The sample URL is in the report, I believe it will be invalid after a few hours, but I can generate a new one anytime, just let me know.
Using
--compat-options no-external-downloader-progress
works around these behaviors.Provide verbose output that clearly demonstrates the problem
yt-dlp -vU <your command line>
)[debug] Command-line config
) and insert it belowComplete Verbose Output
The text was updated successfully, but these errors were encountered: