Issue metadata
Sign in to add a comment
|
JNI DETECTED ERROR IN APPLICATION: bad arguments passed to void org.chromium.content.browser.ContentViewCore.updateImeAdapter |
||||||||||||||||||||||
Issue descriptionVersion: 52.0.2708.0 OS: Android 6.0.1; Nexus 7 What steps will reproduce the problem? (1) Set parameter to build official. (2) ninja -C out/Debug -j3000 -l300 chrome_uiautomator_test_apk (3) out/Debug/bin/run_chrome_uiautomator_test_apk -f CrashReportTest#testChromeCrash What is the expected output? Clankium should not crash, except purposely crashing clankium using chrome://crash in the testcase. The testcase passed before I did sync. What do you see instead? Clankium crashed before even going to chrome://crash. 04-13 11:01:47.181 6626 6644 I chromium: 04-13 11:01:47.195 6601 6601 E art : JNI ERROR (app bug): expected jboolean (0/1) but got value of 98 as argument 10 to void org.chromium.content.browser.ContentViewCore.updateImeAdapter(long, int, int, java.lang.String, int, int, int, int, boolean, boolean) 04-13 11:01:47.253 6601 6601 F art : art/runtime/java_vm_ext.cc:410] JNI DETECTED ERROR IN APPLICATION: bad arguments passed to void org.chromium.content.browser.ContentViewCore.updateImeAdapter(long, int, int, java.lang.String, int, int, int, int, boolean, boolean) (see above for details) 04-13 11:01:47.253 6601 6601 F art : art/runtime/java_vm_ext.cc:410] from void org.chromium.base.SystemMessageHandler.nativeDoRunLoopOnce(long, long) 04-13 11:01:47.253 6601 6601 F art : art/runtime/java_vm_ext.cc:410] "main" prio=5 tid=1 Runnable 04-13 11:01:47.253 6601 6601 F art : art/runtime/java_vm_ext.cc:410] | group="main" sCount=0 dsCount=0 obj=0x74004fa0 self=0xb4df6500 04-13 11:01:47.253 6601 6601 F art : art/runtime/java_vm_ext.cc:410] | sysTid=6601 nice=-4 cgrp=default sched=0/0 handle=0xb6ff7b34 04-13 11:01:47.253 6601 6601 F art : art/runtime/java_vm_ext.cc:410] | state=R schedstat=( 0 0 0 ) utm=602 stm=66 core=2 HZ=100 04-13 11:01:47.253 6601 6601 F art : art/runtime/java_vm_ext.cc:410] | stack=0xbe3bb000-0xbe3bd000 stackSize=8MB 04-13 11:01:47.253 6601 6601 F art : art/runtime/java_vm_ext.cc:410] | held mutexes= "mutator lock"(shared held) 04-13 11:01:47.253 6601 6601 F art : art/runtime/java_vm_ext.cc:410] native: #00 pc 00370e01 /system/lib/libart.so (art::DumpNativeStack(std::__1::basic_ostream<char, std::__1::char_traits<char> >&, int, char const*, art::ArtMethod*, void*)+160) The crash is also uploaded to chromecrash. Here: https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_Android%27%20AND%20ReportID%3D%2779e697c400000000%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D&stbtiq=&reportid=&index=0
,
Apr 13 2016
I ran the testcase a few times and it fails consistently. Here is another crash uploaded to chromecrash. https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_Android%27%20AND%20ReportID%3D%270f1241a200000000%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D&stbtiq=&reportid=&index=0
,
Apr 13 2016
+ current stability sheriff in case this looks familiar. This happens when hzl@ runs some uiautomator test case locally.
,
Apr 14 2016
Havne't seen anything like it but looks strange to me. |is_non_ime_change| is a bool in C++ land, so now sure how it'd be gettin ga vlaue of 98
,
Apr 14 2016
I saw another bug here: https://bugs.chromium.org/p/chromium/issues/detail?id=602706, that looks similar.
,
Apr 14 2016
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by hzl@chromium.org
, Apr 13 20161.8 MB
1.8 MB View Download