{"issue":{"state":"open","created_at":"2011-09-20T21:08:05Z","updated_at":"2011-11-28T20:58:24Z","user":{"gravatar_id":"e1b7068ecf241bc15f79758de78b421d","id":41661,"url":"https://api.github.com/users/sctb","avatar_url":"https://secure.gravatar.com/avatar/e1b7068ecf241bc15f79758de78b421d?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"sctb"},"comments":13,"body":"When making a backtrace request to the V8 debugger agent while broken inside a stdin 'data' handler (via exception or debugger statement) the debugger agent responds with header that indicates that an excessively large JSON response will follow (> 25MB). This seems to cause node's CPU utilization to become pegged at ~100% and the response is never completed. This issue was not present in 0aad61e8's parent.\r\n","assignee":null,"id":1691775,"number":1745,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"labels":[{"name":"debugger","color":"e10c02","url":"https://api.github.com/repos/joyent/node/labels/debugger"}],"title":"Commit 0aad61e8 breaks interaction via V8 debugger protocol","closed_at":null,"html_url":"https://github.com/joyent/node/issues/1745","url":"https://api.github.com/repos/joyent/node/issues/1745","milestone":null},"action":"created","comment":{"created_at":"2011-11-28T20:58:24Z","updated_at":"2011-11-28T20:58:24Z","user":{"gravatar_id":"e1b7068ecf241bc15f79758de78b421d","id":41661,"url":"https://api.github.com/users/sctb","avatar_url":"https://secure.gravatar.com/avatar/e1b7068ecf241bc15f79758de78b421d?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"sctb"},"body":"As of 0.6.3, the simple test case that I posted above continues causes the issue. The node debugger is still unable to debug a running web server.","id":2907152,"url":"https://api.github.com/repos/joyent/node/issues/comments/2907152"}}