Browse Source

[debug] Give debug_watcher maximum priority

v0.7.4-release
Ryan Dahl 15 years ago
parent
commit
5468173ce9
  1. 1
      src/node.cc
  2. 3
      src/node.js

1
src/node.cc

@ -1156,6 +1156,7 @@ int main(int argc, char *argv[]) {
// - which will give V8 control so it can handle whatever new message // - which will give V8 control so it can handle whatever new message
// had been received on the debug thread. // had been received on the debug thread.
ev_async_init(&node::debug_watcher, node::DebugMessageCallback); ev_async_init(&node::debug_watcher, node::DebugMessageCallback);
ev_set_priority(&node::debug_watcher, EV_MAXPRI);
// Set the callback DebugMessageDispatch which is called from the debug // Set the callback DebugMessageDispatch which is called from the debug
// thread. // thread.
Debug::SetDebugMessageDispatchHandler(node::DebugMessageDispatch); Debug::SetDebugMessageDispatchHandler(node::DebugMessageDispatch);

3
src/node.js

@ -351,7 +351,8 @@ var events = eventsModule.exports;
var nextTickQueue = []; var nextTickQueue = [];
var nextTickWatcher = new process.IdleWatcher(); var nextTickWatcher = new process.IdleWatcher();
nextTickWatcher.setPriority(process.EVMAXPRI); // max priority // Only debugger has maximum priority. Below that is the nextTickWatcher.
nextTickWatcher.setPriority(process.EVMAXPRI-1);
nextTickWatcher.callback = function () { nextTickWatcher.callback = function () {
var l = nextTickQueue.length; var l = nextTickQueue.length;

Loading…
Cancel
Save