Death Before Confusion (was: [whatwg] Handling out of memory issues with getImageData/createImageData)
fpizlo at apple.com
Mon Sep 28 06:06:05 UTC 2015
I don't think that prevents a caller from adversarially injecting - and then catching - faults into a callee in such a way that the caller can control which part of the callee runs and which part doesn't. The ability to catch the fault is what causes the security issues, since the caller can keep running even when the callee was forced to give up.
Being able to detect and act upon low memory conditions is helpful in other ways, but I don't think it prevents the bad scenario from happening.
> On Sep 27, 2015, at 4:47 PM, Ron Waldon <jokeyrhyme at gmail.com> wrote:
> Android has an older onLowMemory() callback and a newer onTrimMemory() callback:
> - http://developer.android.com/reference/android/content/ComponentCallbacks.html#onLowMemory()
> - http://developer.android.com/reference/android/content/ComponentCallbacks2.html#onTrimMemory(int)
> iOS has something similar as well.
> Is making these available in ECMAScript proper or an annex a potential solution to this class of problem?
> es-discuss mailing list
> es-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss