Erlang on Android
Sat Sep 18 11:12:01 CEST 2021
Thanks, I guess I'll have to dig into the code to understand better. There
must be a reason why OTP doesn't just fork early in the boot process to
keep around another (or multiple other) child processes for the
erl_child_setup use case. Maybe there is/was a platform where that is not
an option. Once I get more time or when this gets urgent I'll revisit.
Anyone knows about iPhone targets?
Mikael Pettersson <mikpelinux@REDACTED> schrieb am Fr., 17. Sep. 2021,
> On Fri, Sep 17, 2021 at 1:45 PM Dominic Letz <dominic@REDACTED> wrote:
> > So this brings me to my question #1. Is there a way to remove the
> dependency on these external binaries of erl_child_setup [...]
> As I recall, erl_child_setup is there to avoid needing to fork()
> inside the Erlang VM (when spawning off external commands via e.g.
> os:cmd/1). Forking is a problem when one runs massively large
> Erlang/VM instances, as we (Klarna) do. With erl_child_setup, the
> fork() is done inside that much smaller helper process. So I think it
> needs to stay, but the mechanics of starting it might need adapting
> for Android.
> I take it you don't use heart, because that's also a separate executable.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions