Comment #7 on issue 1670 by mikhail.naganov: Unable to pause/resume profiler using debugger protocol
http://code.google.com/p/v8/issues/detail?id=1670
Yes, you need to run with both flags: --prof --noprof-auto. Sorry if that was unclear.
Explaining why log continues to grow. There are two streams of profiling events: code updates and tick events. Code updates occur because code is being dynamically compiled and moved around by GC, and they are needed to be able to map addresses to function names. Tick events occur when VM is being sampled -- they contain captured stack traces. When you pause profiling only sampling is stopped, code updates are continued to be reported, so log processor can still update code mappings.
If you are required to avoid log growth during profiler pauses, there is another option: run with "--prof --prof_lazy". This mode doesn't emit any events when profiling is paused, but to make code mapping possible on profiling resume a whole current code map is being dumped. Also, this mode emits "profiler,pause" and "profiler,resume" into the log.
-- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
