Referring to this thread:
https://groups.google.com/forum/#!searchin/v8-users/profiling$20line$20numbers|sort:relevance/v8-users/C8HEYUx7RFs/l7fJD1ebBAAJ
I changed my code to turn on profiling before compiling the script. It
didn't completely eliminate the hang, and it made it harder to
Ben,
Thanks for the tip. I'll look into that option.
In general we are open to upgrade to a later release as long as we don't
introduce incompatibilities. Good to know that certain bug fixes are
back-ported with Node.js LTS releases.
Jane
On Saturday, August 20, 2016 at 3:43:54 AM UTC-7,
On Sat, Aug 20, 2016 at 2:23 AM, Jane Chen wrote:
> Embedding v8 4.6.88.
>
> Seeing a hang on Windows during cpu profiling. The hang happens in any
> random place calling v8, such as Isolate::New, Context::New etc. Running
> optimized build, my stack doesn't show v8 frames.
Embedding v8 4.6.88.
Seeing a hang on Windows during cpu profiling. The hang happens in any
random place calling v8, such as Isolate::New, Context::New etc. Running
optimized build, my stack doesn't show v8 frames.
Not sure whether it's relevant, I captured this stack once during a hang