[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Chicken-hackers] [PATCH] Drop parent process continuation after fork to
From: |
Peter Bex |
Subject: |
[Chicken-hackers] [PATCH] Drop parent process continuation after fork to allow better collection of garbage |
Date: |
Fri, 10 Nov 2017 21:49:59 +0100 |
User-agent: |
NeoMutt/20170113 (1.7.2) |
Hi all,
I've been working on (or rather, struggling with) with the scsh-process egg
for a bit the past couple of days, and I've been thinking about fork.
It's probably better if we clean up the parent process state that's lying
around in the child's continuation of a (process-fork) call which we will
never call anyway.
This should avoid issues like we've seen with #1367 when forking lots of
processes, and in general decrease memory use of child processes.
Initially I thought I could just (##sys#call-with-cthulhu thunk) because
the C_termination_continuation also exits with code 0, but then
I remembered that (exit) will call ##sys#exit-handler (which the C code
will not do), so I think this patch is correct.
Both for master and chicken-5.
Cheers,
Peter
0001-Similar-to-118fce-and-596332-clean-up-old-state-upon.chicken-5.patch
Description: Text Data
0001-Similar-to-118fce-and-596332-clean-up-old-state-upon.master.patch
Description: Text Data
signature.asc
Description: PGP signature
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Chicken-hackers] [PATCH] Drop parent process continuation after fork to allow better collection of garbage,
Peter Bex <=