[axel-devel] [axel-Bugs][311562] Memory issues using axel-kapt

[axel-bugs at alioth.debian.org]

Bugs item #311562, was opened at 2009-03-28 18:57
>Status: Closed
>Priority: 2
Submitted By: Nobody (None)
Assigned to: Nobody (None)
Summary: Memory issues using axel-kapt 


Initial Comment:
I tried Axel on Ubuntu 8.10, using the package from the Ubuntu repositories.  Unfortunately, when I started the application, it instantly consumed 4 gigs of ram, slowing my computer to a crawl.  I had trouble even opening the system manager, and ultimately had to login to a virtual terminal in order to kill the process. I have no idea what went wrong, but wanted to inform you of the problem I had so that you might be able to check it out.

----------------------------------------------------------------------

>Comment By: Philipp Hagemeister (phihag-guest)
Date: 2009-04-01 22:56

Message:
This is a bug in kaptain, see https://sourceforge.net/tracker/?func=detail&aid=2725833&group_id=12051&atid=112051 . I committed a questionable workaround in rev99.

However, axel as we're developing it is a a CLI program, and will become a library. We will likely remove this GUI in the next major version and replace it with a real one, not a graphical CLI interface.

----------------------------------------------------------------------

Comment By: Philipp Hagemeister (phihag-guest)
Date: 2009-04-01 21:43

Message:
Oh, this is the kapt interface. Somehow managed to overread that.

----------------------------------------------------------------------

Comment By: Giridhar Appaji Nag Yasa (appaji)
Date: 2009-04-01 08:36

Message:
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=378546
And https://bugs.launchpad.net/ubuntu/+source/axel/+bug/236837

----------------------------------------------------------------------

Comment By: Philipp Hagemeister (phihag-guest)
Date: 2009-03-28 19:07

Message:
I don't think we do even allocate a variable number of memory anywhere (except when using the search feature), but I'll look into it. Thanks for reporting!

----------------------------------------------------------------------

You can respond by visiting: 
http://alioth.debian.org/tracker/?func=detail&atid=413085&aid=311562&group_id=100070