This was exposed and discussed here:
https://code.google.com/p/chromium/issues/detail?id=376802
Current plan is to address this by converting all allocation functions
(vpx_memalign, vpx_malloc, vpx_calloc, vpx_realloc) to take 64 bit numbers and
to insure that if we are in a 32 bit that the allocation properly fails.
Please look at webp ( safealloc) code.
Original issue reported on code.google.com by jimbankoski@google.com on 25 Jun 2014 at 11:41
Original issue reported on code.google.com by
jimbankoski@google.com
on 25 Jun 2014 at 11:41