Skip Menu |

This queue is for tickets about the Forks-Super CPAN distribution.

Report information
The Basics
Id: 105130
Status: stalled
Priority: 0/
Queue: Forks-Super

People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in:
  • 0.74
  • 0.75
  • 0.76
Fixed in: (no value)



Subject: Forks-Super-0.64 kills my Debian/jessie VM
See subject. While trying to install the distribution it seems that a lot of resources are consumed, killing some system processes like sshd or the VirtualBox management process. The last thing I see in the terminal is: Gathering information on current system linux.5.020001 and creating Forks::Super::SysInfo package. Creating Forks/Super/SysInfo.pm file SysInfo.pm.PL: creating system-limits file. 1: sleep and alarm are compatible on this system There are 1 cpus on this system. Can open 65532 file handles simultaneously Default socket capacity is about 212992 bytes Default pipe capacity is about 65536 bytes advisory filelocking available for ipc synchronization
On 2015-06-09 14:11:29, SREZIC wrote: Show quoted text
> See subject. While trying to install the distribution it seems that a > lot of resources are consumed, killing some system processes like sshd > or the VirtualBox management process. > > The last thing I see in the terminal is: > > Gathering information on current system linux.5.020001 > and creating Forks::Super::SysInfo package. > Creating Forks/Super/SysInfo.pm file > SysInfo.pm.PL: creating system-limits file. > 1: sleep and alarm are compatible on this system > There are 1 cpus on this system. > Can open 65532 file handles simultaneously > Default socket capacity is about 212992 bytes > Default pipe capacity is about 65536 bytes > advisory filelocking available for ipc synchronization
And /var/log/messages reveals that oom-killer was invoked...
Subject: Forks-Super-0.74 kills my Debian/jessie VM
From the Forks-Super build directory, what is the output of grep maxfork t/out/limits* ?
On 2015-06-09 16:07:20, MOB wrote: Show quoted text
> From the Forks-Super build directory, what is the output of > > grep maxfork t/out/limits* > > ?
maxfork:299
On 2015-06-09 16:13:58, SREZIC wrote: Show quoted text
> On 2015-06-09 16:07:20, MOB wrote:
> > From the Forks-Super build directory, what is the output of > > > > grep maxfork t/out/limits* > > > > ?
> > maxfork:299
This VM has 2GB RAM and 0.7GB Swap. On another VM, with Debian/wheezy running, the maxfork value is higher: 1999. I have no problems here, but that VM has also much more RAM (16GB).
Made some efforts in 0.75 and 0.76 to have system-limits.PL be able to crash without taking down the other build processes. I'll see what I can do about making a crippled VM to test it.
On 2015-07-13 15:57:55, MOB wrote: Show quoted text
> Made some efforts in 0.75 and 0.76 to have system-limits.PL be able to > crash without taking down the other build processes. I'll see what I > can do about making a crippled VM to test it.
I don't see any changes with 0.76. I tried Forks-Super on another VM running debian/wheezy and the same memory+swap settings and had no problem; system-limits was creating 2000 processes. So it looks like something changed in debian/jessie.
This problem should have improved since 0.75. I'll keep this open and see if any other complaints come in.