Package: ruby1.9.1 Version: 1.9.3.194-5 Severity: important Tags: upstream patch
Dear Maintainer, There is a bug in the way the great VM lock is re-initialized after a fork() of a ruby process with multiple POSIX threads happens; the state of the Great VM Lock is only partially re-initialized, leading to a possible deadlock of the child process. We have seen this bug using Debian's version in a pool of heavily-forking resque workers. There is already a fix upstream in trunk (r38819), backported to 1.9.3 (r38832). The fix is a trivial one-liner. For a more detailed description of the issue together with the patch, please refer to ruby bug #7693[1]. Regards, Apollon [1] https://bugs.ruby-lang.org/issues/7693 -- System Information: Debian Release: 7.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing'), (90, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ruby1.9.1 depends on: ii libc6 2.13-37 ii libruby1.9.1 1.9.3.194-5 ruby1.9.1 recommends no packages. Versions of packages ruby1.9.1 suggests: ii graphviz 2.26.3-12 pn ri1.9.1 <none> pn ruby-switch <none> ii ruby1.9.1-dev 1.9.3.194-5 pn ruby1.9.1-examples <none> -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
