Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-7500] Unable to run android applications in emulator from TiStudio with V8 runtime

GitHub Issuen/a
TypeBug
PriorityHigh
StatusClosed
ResolutionFixed
Resolution Date2012-02-14T23:29:04.000+0000
Affected Version/sRelease 2.0.0
Fix Version/sSprint 2012-03, Release 2.0.0, Release 1.8.2
ComponentsAndroid
Labelsregression
ReporterVishal Duggal
AssigneeJosh Roesslein
Created2012-02-01T12:32:47.000+0000
Updated2012-02-14T23:29:04.000+0000

Description

When trying to run an mobile application for Android through TiStudio, the application keeps recycling and I see the following message in the console repeatedly
W/dalvikvm(  411): JNI WARNING: 0x6f746172 is not a valid JNI reference
W/dalvikvm(  411):              in Lorg/appcelerator/kroll/runtime/v8/V8Runtime;.nativeIdle ()V (CallObjectMethodV)
I/dalvikvm(  411): "KrollRuntimeThread" prio=5 tid=10 RUNNABLE
I/dalvikvm(  411):   | group="main" sCount=0 dsCount=0 obj=0x40593bd8 self=0x2ce860
I/dalvikvm(  411):   | sysTid=421 nice=0 sched=0/0 cgrp=default handle=2853128
I/dalvikvm(  411):   | schedstat=( 1876923190 395373034 89 )
I/dalvikvm(  411):   at org.appcelerator.kroll.runtime.v8.V8Runtime.nativeIdle(Native Method)
I/dalvikvm(  411):   at org.appcelerator.kroll.runtime.v8.V8Runtime.access$000(V8Runtime.java:25)
I/dalvikvm(  411):   at org.appcelerator.kroll.runtime.v8.V8Runtime$1.queueIdle(V8Runtime.java:74)
I/dalvikvm(  411):   at android.os.MessageQueue.next(MessageQueue.java:164)
I/dalvikvm(  411):   at android.os.Looper.loop(Looper.java:117)
I/dalvikvm(  411):   at org.appcelerator.kroll.KrollRuntime$KrollRuntimeThread.run(KrollRuntime.java:102)
I/dalvikvm(  411): 
E/dalvikvm(  411): VM aborting
Attaching Console log

Attachments

FileDateSize
ConsoleLog.txt2012-02-01T12:32:47.000+000064030

Comments

  1. Josh Roesslein 2012-02-03

    [PR #1339](https://github.com/appcelerator/titanium_mobile/pull/1339) sent. To test create a mobile application in Studio. Run the generated application on emulator. The application should not crash due to an invalid JNI reference error.
  2. Eric Merriman 2012-02-03

    Verified fixed with SDK 1.9.0.v20120203160134 with emulator 3.0 and 2.3.3.

JSON Source