Jeremy Apthorp
829b230b85
fix: initialize tracing controller before starting platform ( #14499 )
2018-09-11 20:24:03 +02:00
deepak1556
ea7e273a06
gin: Make gin/ remember external reference table
...
https://chromium-review.googlesource.com/c/chromium/src/+/778741
2018-06-19 11:49:42 +10:00
Jeremy Apthorp
73ac019882
Fix up #includes to work with both GYP and GN
2018-05-10 13:38:40 -07:00
Jeremy Apthorp
f1587da480
[chromium-style] out-of-line default constructors and destructors
2018-04-19 11:12:58 -07:00
Jeremy Apthorp
a635f078c6
[chromium-style] auto variable type must not deduce to a raw pointer type
2018-04-19 11:10:52 -07:00
Shelley Vohr
c6f4bbd143
also format missing .cc files
2018-04-18 20:48:45 -04:00
shelley vohr
0e5b6f9300
Upgrade to node v9.3.0 ( #11507 )
...
* update submodule refs for node v9.3.0
* Define "llvm_version" for Node.js build
* NODE_MODULE_CONTEXT_AWARE_BUILTIN -> NODE_BUILTIN_MODULE_CONTEXT_AWARE
* update NodePlatform to MultiIsolatePlatform
* fix linting error
* update node ref
* REVIEW: Explicitly register builtin modules
https://github.com/nodejs/node/pull/16565
* update libcc ref
* switch libcc to c62
* REVIEW: Address node api changes
- Always start the inspector agent for https://github.com/nodejs/node/pull/17085
- Set the tracing controller for node https://github.com/nodejs/node/pull/15538
- Isolate data creation now requires plaform https://github.com/nodejs/node/pull/16700
2018-02-23 10:22:00 +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
dd3d791cb9
IsolateHolder API has been changed
2017-04-27 16:34:52 +09:00
Cheng Zhao
a0605275b9
Clean up node environment on exit in main process
2017-03-02 17:19:00 +09:00
Kevin Sawicki
a2f0111205
Remove v8debug flag no longer supported by node
2016-08-26 12:08:18 -07:00
Cheng Zhao
ee28f4fc32
Handle v8::MicrotasksScope in the main process
2016-06-24 14:45:31 +09:00
Cheng Zhao
5fae63a2f5
Fix compilation errors on OS X
2016-03-10 17:06:21 +09:00
Cheng Zhao
78934dceb9
Cleanup and docs for the --js-flags
2015-11-13 12:22:08 +08:00
Shawn K
fb5beb9af5
Add --js-flags support for main thread.
...
Allow use of flags that must be set before V8 is initialized, such as
"--harmony_proxies", e.g. --js-flags="--harmony_proxies
--harmony_collections"
2015-11-12 01:48:23 -08:00
Robo
7b5a1b06ba
debugger: expose v8debug
2015-10-22 16:20:48 +05:30
Cheng Zhao
2d410ede48
Initialize things in the same sequence with main process
2015-10-21 16:24:54 +08:00
Haojian Wu
d003b1bb57
LoadV8Snapshot has been moved from gin::IsolateHolder to gin::V8Initializer.
2015-08-11 09:48:29 +08: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
Cheng Zhao
10823eeeaa
Fix compilation errors caused by Chrome 39
2014-12-07 07:43:26 -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
