About Process Crashed Error

[omeerkorkmazz]

Hi,

I want to use acvtool for code coverage while testing my application via Appium. I started the tool with the command "acv start ". After that, I wanted to run my test cases that I have written before by using Appium. When I started to Appium, I got this error.

INSTRUMENTATION_RESULT: shortMsg=Process crashed.
INSTRUMENTATION_CODE: 0

How can I find the information related the error? I can not use acvtool by running test cases automatically as you mentioned in document. However, it is working manually.

Thanks,

[pilgun]

Hi @omeerkorkmazz, probably you can find some information in logcat.

I have not tried Appium with ACVTool, but potentially there can be a conflict if Appium wants to use instrumentation process.

[omeerkorkmazz]

Hi @pilgun ,
Thank you for answering. In the documentation, you mentioned that you can test manually or automatically. So, in this situation, how can we run test cases automatically after starting acvtool? I just wondered how you tested automatically and got the report after testing?

[pilgun]

I used automated input generators such as Monkey and Sapienz.

[skyridertk]

I used automated input generators such as Monkey and Sapienz.

So what should we do there? How can we restart the process without stopping the acvtool?

[pilgun]

Every time you start -> test your app -> stop -> generate report. And then you need again start process if you want to continue testing.

[khorrom-khan]

Hi @pilgun ,

I am having the same problem? My tool starts the app process for every new test case. By doing start -> test your app -> stop -> generate report I will get the report for a single run/test case. Is there any way to generate a single cumulative report for multiple runs/test cases or is there any way to restart the process without stopping the acvtool?

[pilgun]

Hi @khorrom-khan, It is possible to generate cumulative report based on several tests. You have to run each test suit separately and accumulate .ec file for each test. Then put all .ec files into a single directory and generate report with -ec parameter pointing to the directory.

…

[khorrom-khan]

This is the code of how I am opening the app using Appium.

`from appium import webdriver

desired_caps = {
"platformName": "Android",
"deviceName": "Android Emulator",
'appPackage': 'org.tomdroid',
'appActivity': 'org.tomdroid.ui.Tomdroid',
"udid": "emulator-5554"
}

driver = webdriver.Remote("http://localhost:4723/wd/hub", desired_caps)`

ACVTool crashes immediately after the application is launched. I have added the Logcat message below. Is there any way to fix this issue and integrate your tool with Appium? It would be really helpful since Appium is a popular testing tool both in the industry and research community.

2020-02-13 15:47:33.819 5253-5253/? I/Radio-JNI: register_android_hardware_Radio DONE 2020-02-13 15:47:33.823 5253-5253/? D/AndroidRuntime: Calling main entry com.android.commands.pm.Pm 2020-02-13 15:47:33.825 5253-5253/? I/art: System.exit called, status: 1 2020-02-13 15:47:33.825 5253-5253/? I/AndroidRuntime: VM exiting with result code 1. 2020-02-13 15:47:33.901 1673-1700/system_process I/PackageManager.DexOptimizer: Running dexopt (dex2oat) on: /data/app/vmdl1863826351.tmp/base.apk pkg=io.appium.unlock isa=x86_64 vmSafeMode=false debuggable=true target-filter=interpret-only oatDir = /data/app/vmdl1863826351.tmp/oat sharedLibraries=null 2020-02-13 15:47:33.910 5277-5277/? W/dex2oat: Unexpected CPU variant for X86 using defaults: x86_64 2020-02-13 15:47:33.911 5277-5277/? I/dex2oat: /system/bin/dex2oat --compiler-filter=interpret-only --debuggable 2020-02-13 15:47:33.935 5277-5277/? I/dex2oat: dex2oat took 24.911ms (threads: 4) arena alloc=2368B (2368B) java alloc=86KB (88208B) native alloc=917KB (939600B) free=1130KB (1157552B) 2020-02-13 15:47:33.937 1673-1700/system_process W/PackageManager: Attempt to re-install io.appium.unlock without first uninstalling. 2020-02-13 15:47:33.937 1673-1687/system_process I/ActivityManager: Force stopping io.appium.unlock appid=10154 user=-1: installPackageLI 2020-02-13 15:47:33.938 1673-2203/system_process D/PackageInstaller: Ignoring abandon after commit relinquished control 2020-02-13 15:47:33.962 1673-1700/system_process I/PackageManager.DexOptimizer: Running dexopt (dex2oat) on: /data/app/vmdl1646271694.tmp/base.apk pkg=io.appium.unlock isa=x86_64 vmSafeMode=false debuggable=true target-filter=interpret-only oatDir = /data/app/vmdl1646271694.tmp/oat sharedLibraries=null 2020-02-13 15:47:33.972 5288-5288/? W/dex2oat: Unexpected CPU variant for X86 using defaults: x86_64 2020-02-13 15:47:33.972 5288-5288/? I/dex2oat: /system/bin/dex2oat --compiler-filter=interpret-only --debuggable 2020-02-13 15:47:33.997 5288-5288/? I/dex2oat: dex2oat took 25.691ms (threads: 4) arena alloc=2368B (2368B) java alloc=90KB (92176B) native alloc=917KB (939624B) free=1130KB (1157528B) 2020-02-13 15:47:33.999 1673-1700/system_process W/PackageManager: Attempt to re-install io.appium.unlock without first uninstalling. 2020-02-13 15:47:33.999 1673-1687/system_process I/ActivityManager: Force stopping io.appium.unlock appid=10154 user=-1: installPackageLI 2020-02-13 15:47:34.000 1673-1684/system_process D/PackageInstaller: Ignoring abandon after commit relinquished control 2020-02-13 15:47:34.152 5295-5295/? D/AndroidRuntime: >>>>>> START com.android.internal.os.RuntimeInit uid 2000 <<<<<< 2020-02-13 15:47:34.153 5295-5295/? D/AndroidRuntime: CheckJNI is ON 2020-02-13 15:47:34.164 5295-5295/? W/art: Unexpected CPU variant for X86 using defaults: x86_64 2020-02-13 15:47:34.166 5295-5295/? D/ICU: No timezone override file found: /data/misc/zoneinfo/current/icu/icu_tzdata.dat 2020-02-13 15:47:34.175 5295-5295/? E/memtrack: Couldn't load memtrack module (No such file or directory) 2020-02-13 15:47:34.175 5295-5295/? E/android.os.Debug: failed to load memtrack module: -2 2020-02-13 15:47:34.175 5295-5295/? I/Radio-JNI: register_android_hardware_Radio DONE 2020-02-13 15:47:34.181 5295-5295/? D/AndroidRuntime: Calling main entry com.android.commands.wm.Wm 2020-02-13 15:47:34.182 5295-5295/? D/AndroidRuntime: Shutting down VM 2020-02-13 15:47:34.355 5309-5309/? D/AndroidRuntime: >>>>>> START com.android.internal.os.RuntimeInit uid 2000 <<<<<< 2020-02-13 15:47:34.356 5309-5309/? D/AndroidRuntime: CheckJNI is ON 2020-02-13 15:47:34.366 5309-5309/? W/art: Unexpected CPU variant for X86 using defaults: x86_64 2020-02-13 15:47:34.368 5309-5309/? D/ICU: No timezone override file found: /data/misc/zoneinfo/current/icu/icu_tzdata.dat 2020-02-13 15:47:34.377 5309-5309/? E/memtrack: Couldn't load memtrack module (No such file or directory) 2020-02-13 15:47:34.377 5309-5309/? E/android.os.Debug: failed to load memtrack module: -2 2020-02-13 15:47:34.377 5309-5309/? I/Radio-JNI: register_android_hardware_Radio DONE 2020-02-13 15:47:34.382 5309-5309/? D/AndroidRuntime: Calling main entry com.android.commands.am.Am 2020-02-13 15:47:34.384 1673-1946/system_process I/ActivityManager: Force stopping org.tomdroid appid=10164 user=0: from pid 5309 2020-02-13 15:47:34.384 1673-1946/system_process I/ActivityManager: Killing 5134:org.tomdroid/u0a164 (adj 0): stop org.tomdroid 2020-02-13 15:47:34.384 1673-1946/system_process D/ActivityManager: cleanUpApplicationRecord -- 5134 2020-02-13 15:47:34.384 1673-1946/system_process W/ActivityManager: Crash of app org.tomdroid running instrumentation ComponentInfo{org.tomdroid/tool.acv.AcvInstrumentation} 2020-02-13 15:47:34.384 1673-1946/system_process I/ActivityManager: Force stopping org.tomdroid appid=10164 user=0: finished inst

[jwlin]

Having the same problem with Appium. ACVTool crashes immediately after the app is launched. Any hints to resolve this issue is appreciated.

[pilgun]

I guess Appium uses instrumentation that finalizes/crashes the instrumentation process created by ACVTool. I still believe it is possible to use them together but you may need to tweak both Appium and ACVTool.

[pilgun]

Solved in the related issue #28