deepak1556
88e53b1b5e
REVIEW: destroy process singleton on sequence where IO is allowed
2018-01-02 16:37:07 +09:00
Cheng Zhao
c0c2461245
Do not create duplicate V8Platform in NodeDebugger
2017-12-22 20:29:09 +09:00
Cheng Zhao
00afeaba9a
Use Node's V8Platform instead of gin's
2017-12-22 20:29:08 +09:00
Cheng Zhao
f4420b449f
Use v8::ArrayBuffer::Allocator inside Node
2017-05-18 16:26:46 +09:00
Cheng Zhao
efe23b7595
Use Node's memory allocator for ArrayBuffer
...
For Buffers created in Node, they are usually allocated in Node and
freed by Chromium's allocator, which will cause crashes when Node and
Chromium are using different allocators.
This commit makes Chromium use Node' allocator for ArrayBuffers.
2017-05-09 14:12:39 +09:00
Cheng Zhao
cf198904a4
Fix cpplint warnings
2017-03-02 17:26:15 +09:00
Cheng Zhao
a0605275b9
Clean up node environment on exit in main process
2017-03-02 17:19:00 +09:00
Cheng Zhao
ee28f4fc32
Handle v8::MicrotasksScope in the main process
2016-06-24 14:45:31 +09:00
Paul Betts
d2944c62a5
basictypes.h => macros.h
2016-03-10 17:06:21 +09:00
Cheng Zhao
d1685f79a2
Initialize V8 in browser process
...
Previously it was initialized by ProxyResolverV8, but after Chrome 43 V8
started to initialize V8 lazily.
2015-05-22 15:30:02 +08:00
Kevin Sawicki
b6b6fc3bfd
Remove All Rights Reserved after GitHub copyright
...
Closes #762
2014-10-31 11:17:05 -07:00
Cheng Zhao
241b07f763
Initailize V8 with gin.
2014-09-01 16:41:26 +08:00
Cheng Zhao
a6ede12cd7
Make sure javascript environment is initialized after ProxyResolverV8.
2014-07-28 20:28:50 +08:00
