SourceForge has been redesigned. Learn more.

#256 spinnig 100% on loopback https


I have encountered pretty much exactly the same symptoms as this bug:
The original reporter of that bug marked it as closed less than a half hour after reporting it because he could not reproduce it on newer versions of aria2. However, it's not clear to me that the bug was ever fixed... I haven't managed to reproduce it on anything newer than aria2 1.9 so far (the original poster produced it on 1.8), but it seems to me to be maybe more complex to reproduce than the original poster thought. So far I have produced it only three times successfully, despite well over a dozen large localhost https transfers.

Is anything known about this issue? Is there a fix for it in newer versions? I'll give more info in the comments in case this is an unknown bug.


  • - 2011-09-27

    So far I have only encountered it on large (4.9+ GB) https localhost transfers, like the original bug report. I encountered it on aria2 1.9.4 on Ubuntu 10.10, similar to but slightly different from the original bug report. So far I have only encountered it when two aria2c instances were downloading the same file at once. In one case both aria2c instances encountered the issue (both on the same 4.99 GB file), in the other case the one instance encountered the issue after the other instance finished running (both on the same 26 GB file). However it appears that the instance that finished running in that case failed to terminate cleanly, so maybe there is more to that story.
    One detail I encountered that the original reporter did not: sometimes paused instances of aria2c will unpause, resume for a minute, then repause. Also, 2 of my 3 instances that paused had their first pause occurred at almost exactly midnight local time... probably just a coincidence.

  • - 2011-09-27

    accidentally submitted this twice by reloading the page, marked the second one as deleted

  • tujikawa

    tujikawa - 2011-09-28

    I'm not sure this bug was fixed in later version because the cause of the error is unknown.
    Could you use latest version and report here if it also exhibits same error?


Log in to post a comment.