Package: dash
Version: 0.5.5.1-1
Severity: critical

Hello,
new dash has some serious problems with waiting on spawned processes, which completely breaks apt-move - at the end apt-move spawns pipe as shown below:

p...@gwy:~$ cat /tmp/err
20768 tty4     S+     0:00      \_ dash /usr/bin/apt-move sync
21840 tty4     S+     0:00          \_ sort
21841 tty4 S+ 0:00 \_ awk -f /usr/share/apt-move/cmpbignum.awk -f /usr/share/apt-move/cmpversion.awk -f /usr/share/apt-move/getdist.awk -f /usr/share/apt-move/get2
21843 tty4     S+     0:00          \_ sort
21844 tty4 D+ 0:00 \_ /usr/bin/awk -f /usr/share/apt-move/pkg1 /tmp/MOVE_lfwAkG/make_pkg_files-fifo1 /tmp/MOVE_lfwAkG/make_pkg_files-contents/unstable/main/binary-i386
21845 tty4     S+     0:00          \_ gzip
21846 tty4 S+ 0:00 \_ tee dists/unstable/main/binary-i386/Packages /tmp/MOVE_lfwAkG/make_pkg_files-fifogz

Once 'tee' completes, it starts consuming 100% CPU, and can be killed only by -9...

p...@gwy:~$ cat /tmp/err2
20768 tty4     R+     0:02      \_ dash /usr/bin/apt-move sync

And strace shows that it is doing endless stream of calls to wait4(), waiting for someone who does not exist anymore:

p...@gwy:~$ head -10 /tmp/err3
wait4(-1, 0xffd236e8, 0, NULL)          = -1 ECHILD (No child processes)
wait4(-1, 0xffd236e8, 0, NULL)          = -1 ECHILD (No child processes)
wait4(-1, 0xffd236e8, 0, NULL)          = -1 ECHILD (No child processes)
wait4(-1, 0xffd236e8, 0, NULL)          = -1 ECHILD (No child processes)
wait4(-1, 0xffd236e8, 0, NULL)          = -1 ECHILD (No child processes)
wait4(-1, 0xffd236e8, 0, NULL)          = -1 ECHILD (No child processes)
wait4(-1, 0xffd236e8, 0, NULL)          = -1 ECHILD (No child processes)
wait4(-1, 0xffd236e8, 0, NULL)          = -1 ECHILD (No child processes)
wait4(-1, 0xffd236e8, 0, NULL)          = -1 ECHILD (No child processes)
wait4(-1, 0xffd236e8, 0, NULL)          = -1 ECHILD (No child processes)
p...@gwy:~$

I suspect that it could be same as bug 515064, but maybe not. In any case, as far as I can tell, severity should be critical as it breaks unrelated package (apt-move). Downgrading back to 0.5.4 fixes the problem.
                                                Thanks,
                                                        Petr



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to