Re: Backporting "MEDIUM: mworker: reexec in waitpid mode after successful loading" to 2.4

2022-05-13 Thread William Lallemand
On Tue, May 10, 2022 at 02:21:42PM +0200, William Lallemand wrote: > On Tue, May 10, 2022 at 12:09:59PM +0200, Christian Ruppert wrote: > > > > It even just happened when running with gdb, without a reload. > > > > What the patch does is re-executing the master in wait-mode once the > worker

Re: Backporting "MEDIUM: mworker: reexec in waitpid mode after successful loading" to 2.4

2022-05-10 Thread William Lallemand
On Tue, May 10, 2022 at 12:09:59PM +0200, Christian Ruppert wrote: > > It even just happened when running with gdb, without a reload. > What the patch does is re-executing the master in wait-mode once the worker was started in order to free the master memory of huge data (maps, SSL certificates

Re: Backporting "MEDIUM: mworker: reexec in waitpid mode after successful loading" to 2.4

2022-05-10 Thread William Lallemand
On Tue, May 10, 2022 at 11:05:01AM +0200, Christian Ruppert wrote: > Hi guys, William, > > can we please get that "MEDIUM: mworker: reexec in waitpid mode after > successful loading" - fab0fdce981149a4e3172f2b81113f505f415595 > backported to 2.4? > I seem to run into it, at least on one of our