On Mon, Nov 21, 2016 at 04:37:12PM +0100, wm4 wrote:
[...]
> Besides, using this in practice would only trigger tons of malloc
> failure handling bugs, so practical uses would probably involve
> tearing down the whole process.
If such bugs exist (no doubt some do) they need to be fixed with or
wit
Le primidi 1er frimaire, an CCXXV, Michael Niedermayer a écrit :
> With this it is possible to prevent OOM with untrusted media
>
> As this fundamentally requires keeping track of allocated memory sizes
> and the memalign hack code does nearly exactly that already, this feature
> depends on it bei
On Mon, 21 Nov 2016 16:18:58 +0100
Michael Niedermayer wrote:
> With this it is possible to prevent OOM with untrusted media
>
> As this fundamentally requires keeping track of allocated memory sizes
> and the memalign hack code does nearly exactly that already, this feature
> depends on it bein
With this it is possible to prevent OOM with untrusted media
As this fundamentally requires keeping track of allocated memory sizes
and the memalign hack code does nearly exactly that already, this feature
depends on it being enabled.
Signed-off-by: Michael Niedermayer
---
libavutil/mem.c | 45
