Hi all, I have been fighting a memory leak in my node server application for some time, but as node-inspector cannot handle the memory snapshots at the moment with the newer v8 versions, I have been trying to help out and fix some things.
It turns out that quite some things changed, so after some fiddling I went to ask in the webkit channel on IRC on documentation on the web inspector. When talking to Pavel Feldman of the web inspector team, he suggested that this kind of problem could be fixed much easier when some of the V8 WebKit bindings to the web inspector would be ported to node, "so that node acted say as a 'worker', hence tip-of-tree inspector front-end would work with it at all times." The result of this would be that node would be a "remote", which could be addressed directly from a webkit browser (like this: http://code.google.com/intl/nl-NL/chrome/devtools/docs/remote-debugging.html). Pavel also said that the inspector team would be willing to assist, but that they needed the node team to be interested / drive the effort. What is your take on this? regards Maurits -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
