lukechilds/node - node - Gitea: Git with a cup of tea

Commit Graph

Author	SHA1	Message	Date
Fedor Indutny	f1de13b8ab	node: do not print SyntaxError hints to stderr Try embedding the ` ... ^` lines inside the `SyntaxError` (or any other native error) object before giving up and printing them to the stderr. fix #6920 fix #1310	11 years ago
Trevor Norris	d9e1e4c661	env: add watched_providers for AsyncListener Now the second field in asyncFlags will tell if the provider is currently being watched, or listened for. Signed-off-by: Timothy J Fontaine <tjfontaine@gmail.com>	11 years ago
Ben Noordhuis	010222d39f	src: add tracing.v8.on('gc') statistics hooks Add a new 'tracing' module with a v8 property that lets the user register listeners for gc events. The listeners are invoked after every garbage collection cycle with 'before' and 'after' statistics. Useful for monitoring tools that want to keep track of memory usage.	11 years ago
Fedor Indutny	e57ab7ba06	node: `EmitExit` should not call `exit()` Before this commit `RunAtExit` and `env->Dispose()` were never reached, because `EmitExit` was always colling `exit`.	11 years ago
Trevor Norris	646ac18d79	node: AsyncListener use separate storage mechanism Before when an AsyncListener object was created and the "create" callback returned a value, it was necessary to construct a new Object with the same callbacks but add a place for the new storage value. Now, instead, a separate storage array is kept on the context which is used for any return value of the "create" callback. This significantly reduces the number of Objects that need to be created. Also added a flags property to the context to quickly check if a specific callback was available either on the context or on the AsyncListener instance itself. Few other minor changes for readability that were difficult to separate into their own commit. This has not been optimized yet.	11 years ago
Trevor Norris	828f14556e	src: revert domain using AsyncListeners This is a slightly modified revert of `bc39bdd`. Getting domains to use AsyncListeners became too much of a challenge with many edge cases. While this is still a goal, it will have to be deferred for now until more test coverage can be provided.	11 years ago
Ben Noordhuis	27f115d715	src: fix Context::Scope usage env->context() may or may not create a new Local. It currently does not but don't depend on that behavior, create a HandleScope first.	11 years ago
Trevor Norris	bc39bdd995	domain: use AsyncListener API The domain module has been switched over to use the domain module API as much as currently possible. There are still some hooks in the EventEmitter, but hopefully we can remove those in the future.	11 years ago
Trevor Norris	efa62fd9cc	node: add AsyncListener support AsyncListener is a JS API that works in tandem with the AsyncWrap class to allow the user to be alerted to key events in the life cycle of an asynchronous event. The AsyncWrap class has its own MakeCallback implementation that core will be migrated to use, and uses state sharing techniques to allow quicker communication between JS and C++ whether the async event callbacks need to be called.	11 years ago
Trevor Norris	4b84e42f67	node: don't share state with in_tick/last_threw There was no need to share state between C++ and JS for these two values. So they have been moved to their respective locations. This will help performance only a tiny bit, but it does help code complexity much more.	12 years ago
Ben Noordhuis	ef4a35bca5	src: update after v8 api changes	11 years ago
Fedor Indutny	7063c59b97	cpplint: disallow comma-first in C++	11 years ago
Ben Noordhuis	57231d5286	src: notify V8 profiler when we're idle Inform V8's CPU profiler when we're idle. The profiler is sampling-based but not all samples are created equal; mark the wall clock time spent in epoll_wait() and friends so profiling tools can filter it out. The samples still end up in v8.log but with state=IDLE rather than state=EXTERNAL.	11 years ago
Ben Noordhuis	a0f79867dc	src: initialize c-ares task list on env init Don't forget to initialize the c-ares task tree head when creating a new Environment. Oversight from the multi-context work that landed in commit `756b622`. Fixes #6244.	11 years ago
Ben Noordhuis	756b622295	src: add multi-context support This commit makes it possible to use multiple V8 execution contexts within a single event loop. Put another way, handle and request wrap objects now "remember" the context they belong to and switch back to that context when the time comes to call into JS land. This could have been done in a quick and hacky way by calling v8::Object::GetCreationContext() on the wrap object right before making a callback but that leaves a fairly wide margin for bugs. Instead, we make the context explicit through a new Environment class that encapsulates everything (or almost everything) that belongs to the context. Variables that used to be a static or a global are now members of the aforementioned class. An additional benefit is that this approach should make it relatively straightforward to add full isolate support in due course. There is no JavaScript API yet but that will be added in the near future. This work was graciously sponsored by GitHub, Inc.	12 years ago

15 Commits (e746bbdc2b79881b2c991c829b5437340583a064)