electron/chromium_src/chrome
Vadim Macagon 7c5d3296e7 Prevent undefined behavior when some Node Buffer objects are destroyed
If node::Buffer::New() is used to wrap an existing chunk of memory
without providing a custom callback to release that memory then Node
will just use `free()`. In a couple of places Node buffer objects were
constructed from chunks of memory that were allocated with `new[]`, but
a custom callback to release that memory was omitted, this resulted in
undefined behavior when those buffers were destroyed because `free()`
was used to release memory allocated with `new[]`.

To avoid undefined behavior the aforementioned buffer objects are now
constructed with a custom callback that safely releases the underlying
chunk of memory.
2016-10-03 10:26:26 +07:00
..
browser Prevent undefined behavior when some Node Buffer objects are destroyed 2016-10-03 10:26:26 +07:00
common Fix building on Windows 2016-09-14 16:22:43 +09:00
renderer Fix building on Windows 2016-09-14 16:22:43 +09:00
utility Fix building on Windows 2016-05-23 16:39:19 +09:00