Running in a separate process space doesn't work very well if you want any
custom function callbacks you might have hooked into v8 to be able to
access or manipulate data that might be used by the rest of your
application, since each process has no access to your main application's
data space.
To be perfectly honest, this seems rather pointless to terminate the
process in this way.
If, in fact, a process were legitimately using too much memory, the
underlying operating system should be entirely capable of killing it
anyways. Having v8 do so of its own accord instead of simply return
unceremoniously kill the process anyways. It is
redundant at best to deliberately put this kind of logic into v8, and at
worst renders v8 unusable for many situations.
On Tuesday, December 4, 2018 at 1:01:36 PM UTC-8, Kenton Varda wrote:
>
> On Tue, Dec 4, 2018 at 12:40 PM markt via v8-users &l
> -Kenton
>
> On Sun, Dec 30, 2018 at 8:47 AM markt via v8-users <
> v8-u...@googlegroups.com > wrote:
>
>> I was not suggesting that v8 be designed to recover from situations where
>> the native process has actually run out of all available memory, I am
>>
