this isn't a profiler module issue given it seems to be an issue with the
v8 log file itself when trying to lazy start profiling, I think this is the
right place to post.
Please see the attached zip for my test case.
I'm trying to profile a node server app, but want to avoid profiling
startup. Therefore, I'm trying to use the prof_lazy support in node/v8.
If I use the --prof support, the profiler works as expected. If I instead
use the --prof_lazy --prof and --log_all, the v8.log is written to, but it
ends up being non-parseable by nprof (from profiler module). It looks like
the problem is that with --prof_lazy node isn't writing out the code that
is loaded until I call profiler.resume() which means all the symbols that
should have been known are not.
I would love for someone to hack the attached test case and driver script
(test.sh) to make the v8-lazystartprofiling.nprof.txt look clean instead of
all the unknown command log entries and get the unaccounted ticks to be
zero. Note the comparable log file v8-standardprofiling.nprof.txt is clean
in these two areas (no unknown commands and all ticks accounted for).
If I can get this working, I will likely throw this up as an example
somewhere. Maybe I'm missing something basic, but I haven't been able to
find a single place that puts all the pieces together in a single example
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@example.com
To unsubscribe from this group, send email to
For more options, visit this group at