:mem_usage ignored

[ghost]

If I have a start_command such as:

#!/usr/bin/env ruby
class Job
  def run
    a = []
    while true; a << 'x' * 1024; end
  end
end

j = Job.new
j.run

The check I have configured never kills it:

process.start_command = './job.rb'
process.checks :mem_usage, below: 20.megabytes, every: 5.seconds, times: 3

The process grows until I kill it manually, well past the 20MB limit I set. Using the :include_children option had no effect.

I have this same issue on Mac OS and Linux.

[mikegee]

I've seen Bluepill kill Sidekiq worker processes for being over the memory limit. So maybe this worked in some previous versions, then broke? If so, git bisect could help narrow down the culprit.

[ghost]

I just spent a couple of hours testing the 0.0.66 version from 2013. I get the exact same behavior. I set a limit of 25 MBs and then I see the process continue to grow well past that limit. Ten minutes later the memory usage is past a GB and bluepill still hasn't killed it.