Ubuntu
axel package

Axel-kapt uses all memory and CPU resources

Bug #236837 reported by Mario Di Nicola on 2008-06-02

Affects		Status	Importance	Assigned to
	Axel	Unknown	Unknown	auto-alioth.debian.org #311811
	axel (Debian)	Fix Released	Unknown	debbugs #378546
	axel (Ubuntu)	Fix Released	Undecided	Unassigned
Nominated for Jaunty by Daniel Gimpelevich

Bug Description

Binary package hint: axel

While running axel-kapt no graphics interface is presented. Instead the CPU and memory usage goes out of control consuming between 70%-100% resources according to top. Information as follows:

apt-cache policy axel-kapt:
axel-kapt:
Installed: 1.0b-3
Candidate: 1.0b-3

lsb_release -rd:
Description: Ubuntu 8.04
Release: 8.04

uname -a:
Linux enterprise 2.6.24-17-generic #1 SMP Thu May 1 13:57:17 UTC 2008 x86_64 GNU/Linux

kdesktop --version:
Qt: 3.3.8b
KDE: 3.5.9
KDesktop: 3.5.9

Located a similar bug with a testing/unstable Debian package here:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=378546

A strace of axel-kapt showing last line in a wait state is attached.

See original description

Revision history for this message

Mario Di Nicola (warp99) wrote on 2008-06-02:

strace_axel-kapt.txt Edit (52.7 KiB, text/plain)

Revision history for this message

Y Giridhar Appaji Nag (appaji) wrote on 2008-06-03:

Which process consumes all the memory and CPU? Is it axel, kaptain or python?

Revision history for this message

Mario Di Nicola (warp99) wrote on 2008-06-18:

"Which process consumes all the memory and CPU? Is it axel, kaptain or python?"

It's kaptain that is consuming all of the resources. Sorry about not including that in my original post.

Mario Di Nicola (warp99) on 2008-07-01

description:

updated

Bug Watch Updater (bug-watch-updater) on 2009-03-11

Changed in axel:
status:	Unknown → Incomplete

Bug Watch Updater (bug-watch-updater) on 2009-03-24

Changed in axel:
status:	Incomplete → Confirmed

Revision history for this message

Y Giridhar Appaji Nag (appaji) wrote on 2009-04-08:

Use @string() Edit (496 bytes, text/plain)

Use @string() instead of @combo, but there isn't choice among terminals to use anymore with this fix.

Revision history for this message

Mario Di Nicola (warp99) wrote on 2009-05-15:

I justed updated to Jaunty then changed my desktop to Gnome and the problem is actually worse. Without the patch the system basically goes into a loop consuming all resources. I'm currently using an Intel 8500 Quad Core CPU and utilization goes to about 95% on all 4 cores. The system becomes so unresponsive that X is completely useless and switching to a terminal, logging in, and trying to kill kaptain is literally at a snails pace.

With the patch everything seems to function as it should sans your choice of terminals. I would suggest that the patch be introduced anyway or the package pulled since the system lockup is now very severe.

Revision history for this message

Daniel Gimpelevich (daniel-gimpelevich) wrote on 2009-07-07:

I just had an ugly, ugly system shutdown from this bug on 64-bit Ubuntu 9.04; ick!

Changed in axel (Ubuntu):
status:	New → Confirmed

Revision history for this message

Daniel Gimpelevich (daniel-gimpelevich) wrote on 2009-07-07:

The associated Debian bug has been fixed and closed. Indeed, rebuilding the Karmic package for Jaunty eliminates it. A patch is included in the Debian bug report.

Revision history for this message

Daniel Gimpelevich (daniel-gimpelevich) wrote on 2009-07-07:

Patch submitted upstream to fix additional bugs.

Bug Watch Updater (bug-watch-updater) on 2011-08-10