[chef] Re: Re: Re: Re: Application cookbook memory leak

[Andrea Campi < >]

On Sat, Nov 24, 2012 at 10:54 AM, Karol Hosiawa < " target="_blank"> > wrote:

The suggestion to use forking is really sweeping the problem under the carpet.
If there's a leak it should be fixed otherwise people using the
application cookbook
not aware of the need to fork chef-client will run into the same problem again.
Forking is also not an option on some platforms/Ruby VMs afaik.
I'll report if I manage to find it.

Oh sure, it's just that it might take a while to find, fix and merge; so I was simply offering a short-term workaround.

But beyond that, of course we want a proper fix.