7c5d3296e7
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. |
||
---|---|---|
.. | ||
extensions | ||
media | ||
printing | ||
profiles | ||
renderer_host/pepper | ||
speech | ||
ui | ||
browser_process.cc | ||
browser_process.h | ||
certificate_manager_model.cc | ||
certificate_manager_model.h | ||
chrome_notification_types.h | ||
chrome_process_finder_win.cc | ||
chrome_process_finder_win.h | ||
process_singleton.h | ||
process_singleton_posix.cc | ||
process_singleton_win.cc |