bew / crystal Goto Github PK

Even though a fork should not copy memory space from the parent process, doing a fork when the compiler uses a lot of memory will most likely result in a fork: cannot allocate memory error.

An idea is to start another process at the start of the compiler, this process will just wait for a command on a pipe, and fork-exec this command on demand. The fork should be very lightweight because this early fork doesn't use a lot of memory.

(need more checks on why fork doesn't do COW with the virtual memory..)

crystal-lang#5427