[eeps] New EEP: setrlimit(2) analogue for Erlang
Thu Feb 7 14:43:38 CET 2013
It is now in the repository as EEP 42:
I rewrote to use code quoting in Markdown i.e backtick quoting
on all code snippets. That made all backslash escapes on underscore
superfluous so I removed them. It made the unprocessed Markdown
file more readable.
In this process I removed a few quotes around 'atoms' that were not
strictly necessary. If those were there for a style reason or you for
any other reason want them back just let me know.
On Thu, Feb 07, 2013 at 11:03:03AM +1300, Richard O'Keefe wrote:
> Just today, I saw Matthew Evans'
> This pertains to a feature I would like to see
> in Erlang. The ability to set an optional
> "memory limit" when a process and ETS table is
> created (and maybe a global optional per-process
> limit when the VM is started). I've seen a few
> cases where, due to software bugs, a process size
> grows and grows; unfortunately as things stand
> today the result is your entire VM crashing -
> hopefully leaving you with a crash_dump.
> Having such a limit could cause the process to
> terminate (producing a OOM crash report in
> erlang.log) and the crashing process could be
> handled with supervisor rules. Even better you
> can envisage setting the limits artificially low
> during testing to catch these types of bugs early on.
> in my mailbox. I have seen too many such e-mail messages.
> Here's a specific proposal. It's time _something_ was done
> about this kind of problem. I don't expect that my EEP is
> the best way to deal with it, but at least there's going to
> be something for people to point to.
> eeps mailing list
/ Raimo Niskanen, Erlang/OTP, Ericsson AB
More information about the eeps