Comment #2 on issue 2006 by [email protected]: Some JSON debugger
lookup requests are taking a very long time
http://code.google.com/p/v8/issues/detail?id=2006
One last repro. In this standalone program, set a breakpoint at line 5
(console.log(a + b)):
#!/usr/bin/env node
var a = 3;
var b = 4;
console.log(a + b);
console.log("About to load reduced project...");
var project = {
packages: function() {
foo('npm ls', function(err, stdout, stderr) {
//var lines = stdout.split('\n')
//var packages = []
//for (var i = 0; i < lines.length; i++) {
// var packageName = lines[i].match(/^(├──|├─┬|└─┬|└──)
(.+)$/)
// if (packageName && packageName[2]) {
// packages.push(packageName[2])
// }
//}
})
}
}
var props = [];
for (var p in project) {
props.push(p);
}
console.log("props(project) : " + props.join(" "))
/// END
At that point, the reqLookup request takes about 30 seconds to
provide a response for ref 0. The JSON response is only 9192 chars,
so that doesn't explain the delay, but I've attached it anyway.
Anyway, that's the delay, and I've seen it in other contexts.
Sometimes v8 takes 29-30.1 seconds to do a lookup on ref 0.
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
