App crashes when V8 profiler is enabled

[slavchev]

App crashes when V8 profiler is enabled via __startCPUProfiler('test');

Logcat output:

08-18 14:44:55.604: I/TNS.Native(7871): NativeScript Runtime Version RUNTIME_VERSION_PLACEHOLDER, commit RUNTIME_COMMIT_SHA_PLACEHOLDER
08-18 14:44:55.604: D/TNS.Native(7871): JNI_ONLoad
08-18 14:44:55.608: D/TNS.Native(7871): JNI_ONLoad END
08-18 14:44:55.608: I/System.out(7871): Sending WAIT chunk
08-18 14:44:55.623: I/art(7871): Debugger is active
08-18 14:44:55.808: I/System.out(7871): Debugger has connected
08-18 14:44:55.808: I/System.out(7871): waiting for debugger to settle...
08-18 14:44:56.009: I/System.out(7871): waiting for debugger to settle...
08-18 14:44:56.209: I/System.out(7871): waiting for debugger to settle...
08-18 14:44:56.409: I/System.out(7871): waiting for debugger to settle...
08-18 14:44:56.610: I/System.out(7871): waiting for debugger to settle...
08-18 14:44:56.810: I/System.out(7871): waiting for debugger to settle...
08-18 14:44:57.010: I/System.out(7871): waiting for debugger to settle...
08-18 14:44:57.210: I/System.out(7871): debugger has settled (1491)
08-18 14:44:57.212: D/TNS.Java(7871): prepareAppBuilderCallbackImpl error: com.tns.internal.AppBuilderCallbackImpl
08-18 14:44:57.220: D/TNS.Java(7871): Sync is enabled:
08-18 14:44:57.220: D/TNS.Java(7871): Sync path              : /data/local/tmp/com.tns.android_runtime_testapp/sync/
08-18 14:44:57.220: D/TNS.Java(7871): Full sync path         : /data/local/tmp/com.tns.android_runtime_testapp/fullsync/
08-18 14:44:57.220: D/TNS.Java(7871): Removed files sync path: /data/local/tmp/com.tns.android_runtime_testapp/removedsync/
08-18 14:44:57.228: D/TNS.Java(7871): Initializing NativeScript JAVA
08-18 14:44:57.228: D/TNS.Java(7871): MakeInstanceStrong (0, class com.tns.NativeScriptApplication)
08-18 14:44:57.228: D/TNS.Java(7871): Initialized app instance id:0
08-18 14:44:57.378: D/TNS.Native(7871): Initializing Telerik NativeScript: app instance id:0
08-18 14:44:57.657: D/TNS.Native(7871): Compiling prepareExtend.js script
08-18 14:44:57.658: D/TNS.Native(7871): Compile prepareExtend.js script
08-18 14:44:57.658: D/TNS.Native(7871): Compiled prepareExtend.js script
08-18 14:44:57.658: D/TNS.Native(7871): Executed prepareExtend.js script
08-18 14:44:57.664: D/TNS.Native(7871): lenNodes=51180, lenNames=467632, lenValues=504734
08-18 14:44:57.664: D/TNS.Native(7871): time=6
08-18 14:44:57.681: D/TNS.Java(7871): getDebuggerPortFromEnvironment
08-18 14:44:57.682: D/TNS.Java(7871): getDebuggerPortFromEnvironment:: shouldEnableDebuggingFlag=true
08-18 14:44:57.688: D/TNS.Java(7871): shouldDebugBreakFlag=false
08-18 14:44:57.689: D/TNS.Java(7871): envInFileFlag=false
08-18 14:44:57.689: D/TNS.Java(7871): port=-1
08-18 14:44:57.689: D/TNS.Java(7871): init time=2689
08-18 14:44:57.700: D/TNS.Native(7871): Compiling script (module /data/data/com.tns.android_runtime_testapp/files/app/app.js)
08-18 14:44:57.701: D/TNS.Native(7871): Compiled script (module /data/data/com.tns.android_runtime_testapp/files/app/app.js)
08-18 14:44:57.702: D/TNS.Native(7871): Running script (module /data/data/com.tns.android_runtime_testapp/files/app/app.js)
08-18 14:44:58.646: V/JS(7871): AndroidApplication is deprecated
08-18 14:44:58.648: V/JS(7871): AndroidApplication is deprecated
08-18 14:44:58.648: V/JS(7871): AndroidApplication is deprecated
08-18 14:44:58.649: V/JS(7871): AndroidApplication is deprecated
08-18 14:44:58.650: V/JS(7871): AndroidApplication is deprecated
08-18 14:44:58.650: V/JS(7871): AndroidApplication is deprecated
08-18 14:44:58.650: V/JS(7871): AndroidApplication is deprecated
08-18 14:44:58.651: V/JS(7871): AndroidApplication is deprecated
08-18 14:44:58.666: V/JS(7871): App.onCreate: 3662
08-18 14:44:59.248: A/libc(7871): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x1ebe in tid 7871 (runtime_testapp)

[rosen-vladimirov]

I believe this could be related to this issue The issue in v8 is here
The problem was reproducible with iojs 3.x and nodejs 4.0
It's been fixed in latest v8 and nodejs versions.

[atanasovg]

We did some research on the matter, I think @slavchev may share some info.

[slavchev]

So far it seems there is a bug in V8 stack unwinding logic (more details at https://groups.google.com/forum/#!topic/v8-users/z8Fz3lsm8iE). As an immediate step we will try to upgrade to the latest V8.

[slavchev]

Closing this issue until further need.