FWIW, I finally fixed my memory leaks using a module I started to write
recently, https://github.com/c4milo/node-webkit-agent. As I mention in the
readme, it's a work in progress and so far cpu and heap profiling are
working just fine. Check it out and let me know if you have any issues!
Best,
Relevant
https://groups.google.com/forum/?fromgroups#!searchin/v8-users/heap$20profiling$20via$20debugger$20agent/v8-users/hI3QMJG4JwU/4RKkT84Y7lkJ
On Thu, Mar 22, 2012 at 2:10 PM, Camilo Aguilar cam...@cloudescape.comwrote:
fwiw, the remote protocol doesn't seem to support profiling yet
On
On Mar 22, 2012, at 3:05 PM, Ben Noordhuis wrote:
On Wed, Mar 21, 2012 at 21:27, Maurits mauritslam...@gmail.com wrote:
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
yes. +1 for node-inspector in core. it's a really useful tool and is a pain
to have to install it separately...
--
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
I think we are talking about including bindings to v8-profiler in nodejs
core, which make complete sense to me, and shouldn't require a lot of
effort if we re-use webkit bindings. In this scenario node-inspector will
be replaced by the web inspector that comes by default in webkit and node
will
I'm also willing to write and/or port these bindings to nodejs.
On Thu, Mar 22, 2012 at 1:33 PM, Camilo Aguilar cam...@cloudescape.comwrote:
I think we are talking about including bindings to v8-profiler in nodejs
core, which make complete sense to me, and shouldn't require a lot of
effort if
fwiw, the remote protocol doesn't seem to support profiling yet
On Thu, Mar 22, 2012 at 1:35 PM, Camilo Aguilar cam...@cloudescape.comwrote:
I'm also willing to write and/or port these bindings to nodejs.
On Thu, Mar 22, 2012 at 1:33 PM, Camilo Aguilar cam...@cloudescape.comwrote:
I think