electron/chromium_src
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
..
chrome Prevent undefined behavior when some Node Buffer objects are destroyed 2016-10-03 10:26:26 +07:00
extensions fix pointer usage 2015-12-11 00:25:25 +05:30
grit Add printing related source codes from chrome. 2014-08-21 15:43:11 +08:00
library_loaders Update the libspeechd_loader 2015-12-08 10:26:32 +08:00
net/test/embedded_test_server Update to API changes of Chrome 52 2016-07-04 15:32:43 +09:00
LICENSE.chromium Move all chromium's code under chromium_src. 2014-06-29 06:06:35 +00:00