Your message dated Sat, 01 Mar 2008 21:25:30 +0100 with message-id <[EMAIL PROTECTED]> and subject line ripperx does not leave processes behind anymore has caused the Debian Bug report #387584, regarding leaves a lot of processes behind to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 387584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=387584 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems
--- Begin Message ---Package: ripperx Version: 2.7.0-2 Severity: normal Hello ! I use ripperx for what it is meant, that is ripping with cdparanoia and encoding with lame. When I quit, I can notice that there are a whole bunch of ripperX_... processes left. That definitely shouldn't be the case, and in the end, it is consuming quite a lot of memory. Here is what I get: 10:30 [EMAIL PROTECTED] ~ ps awuxf | grep ripperX | tail vincent 19774 0.0 0.0 2496 464 ? S 09:06 0:00 ripperX_plugin-lame 181712 19210 vincent 19833 0.0 0.0 2500 472 ? S 09:07 0:00 ripperX_plugin-cdparanoia 320050 2772 vincent 19863 0.0 0.0 2500 472 ? S 09:07 0:00 ripperX_plugin-cdparanoia 322822 20483 vincent 19904 0.0 0.0 2496 468 ? S 09:07 0:00 ripperX_plugin-lame 200922 26208 vincent 20105 0.0 0.0 2500 468 ? S 09:08 0:00 ripperX_plugin-lame 227130 24727 vincent 20314 0.0 0.0 2496 472 ? S 09:09 0:00 ripperX_plugin-lame 251857 24448 vincent 20488 0.0 0.0 2500 468 ? S 09:10 0:00 ripperX_plugin-lame 276305 14222 vincent 20579 0.0 0.0 2496 472 ? S 09:10 0:00 ripperX_plugin-lame 290527 29523 vincent 20795 0.0 0.0 2500 468 ? S 09:11 0:00 ripperX_plugin-lame 320050 2772 vincent 20826 0.0 0.0 2496 468 ? S 09:11 0:00 ripperX_plugin-lame 322822 20483 10:31 [EMAIL PROTECTED] ~ ps awuxf | grep ripperX | wc 133 1730 13344 That make around 100MB of used memory... Killing the processes work fine. I guess that's simply a problem of not closing the child when it finishes it's process... Thanks for considering this report Vincent Fourmond -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.16 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) (ignored: LC_ALL set to en_GB) Versions of packages ripperx depends on: ii cdparanoia 3a9.8-14 An audio extraction tool for sampl ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries ii libglib1.2 1.2.10-10.1 The GLib library of C routines ii libgtk1.2 1.2.10-18 The GIMP Toolkit set of widgets fo ii libid3-3.8.3c2a 3.8.3-5 Library for manipulating ID3v1 and ii libx11-6 2:1.0.0-9 X11 client-side library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxi6 1:1.0.1-3 X11 Input extension library ii vorbis-tools 1.1.1-6 several Ogg Vorbis tools ii zlib1g 1:1.2.3-13 compression library - runtime ripperx recommends no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Version: 2.7.2-2 The newer version of ripperx does not leave any process behind anymore; I'm therefore closing this bug report. Cheers, Vincent -- Vincent Fourmond, Debian Developer http://vince-debian.blogspot.com/ -- pretty boring signature, isn't it ?
--- End Message ---
