chromium on x86 Android

[Demetrios Tsillas]

I built a 60.0.3112.0 based chromium using these instructions:

https://chromium.googlesource.com/chromium/src/+/master/docs/android_build_instructions.md#System-requirements

I'm running the Android Studio emulator (Nexus 5X API 23 2 with Android 6.0 (GoogleAPIs)). Emulator seems to run great.

I install ChromiumPublic.apk using 'adb install ChromiumPublic.apk'. The app seems to install fine and appears in the app list.

But when I run it I see it crashes with "Unfortunately, Chromium has stopped."

Any help appreciated.

-Jim.

[Sunny Sachanandani]

You can run build/android/tombstones.py --output-directory=<path to output directory e.g. out/Debug> in the chromium checkout to get stack traces from android logs. You can also run adb logcat to see android logs but you might have to symbolize stack traces yourself that way.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/e070c944-e0b6-4f2a-8fe6-436b61b0c333%40chromium.org.

[Andrew Grieve]

Also check to ensure hardware accelerated graphics is enabled in the emulator settings

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAKqK8MktdQydMiRTWcRUuxoZtFuAJ7sFNjwFND8_UFZy%3DOBm6A%40mail.gmail.com.

[Alexis Ménard]

Hi,

Make sure you setup the emulator for X86, make sure you install the Intel Hardware Accelerated execution manager (see https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager) and that your emulator has "Use Host GPU” checked.

Thanks

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

[Demetrios Tsillas]

About that..

I adb pull'ed the tombstones and tried running them through stack but I get

/Work/worktree3/src/out/Release_android_x86_64/lib.unstripped/libchrome.so: File format not recognized

[Demetrios Tsillas]

haxm is installed (6.0.6) and I selected Hardware for the GLES emulation. I do not see a "Use Host GPU" setting in the emulator device settings.

[Demetrios Tsillas]

Still hoping someone can help on this.

I tried with 6.0.3182.0 and I see the same problem. Building x86 cpu target for Android will not run on the Android Studio emulator using Android 6.0 (GoogleAPIs) Nexus 5X API 23 with x86 CPU/ABI.

The emulator seems to work fine otherwise.

-Jim.

[Andrew Grieve]

On Fri, Aug 4, 2017 at 1:52 PM, Demetrios Tsillas <jtsi...@gmail.com> wrote:

About that..

I adb pull'ed the tombstones and tried running them through stack but I get

/Work/worktree3/src/out/Release_android_x86_64/lib.unstripped/libchrome.so: File format not recognized

This error almost always means the wrong architecture's toolchain is being used. Maybe try explicitly telling the stack script via "stack --arch=x64" (or x86_64... not sure what it accepts)

 

 

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/0df44f0f-355d-4f8d-abd4-141911fd25a9%40chromium.org.

[Samuel Huang]

Try playing with the -gpu option?

https://developer.android.com/studio/run/emulator-acceleration.html

E.g., -gpu swiftshader

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CABiQX1UUPSciKk_P8MBBt4krZqqTN8fjXyzvdT8t8Z0wM%3Dhy1Q%40mail.gmail.com.

[Demetrios Tsillas]

I tried starting the emulator from the command line and was able to run is with swiftshader option. But still chromium is crashing. Here's the first indication that there's trouble from adb logcat:

08-15 11:15:05.212  3100  3117 E chromium: [ERROR:gl_surface_egl.cc(289)] eglChooseConfig failed with error EGL_SUCCESS

08-15 11:15:05.215  3100  3117 E chromium: [ERROR:gl_surface_egl.cc(289)] eglChooseConfig failed with error EGL_SUCCESS

08-15 11:15:05.233  3100  3117 D EGL_emulation: eglCreateContext: 0xac353160: maj 2 min 0 rcv 2

08-15 11:15:05.234  3100  3117 D EGL_emulation: eglMakeCurrent: 0xac353160: ver 2 0 (tinfo 0xaa94d7f0)

08-15 11:15:05.239  3100  3117 E eglCodecCommon: glUtilsParamSize: unknow param 0x00008cdf

08-15 11:15:05.949  1320  1618 W audio_hw_generic: Not supplying enough data to HAL, expected position 797947 , only wrote 737676

08-15 11:15:12.788  1588  1602 W ActivityManager: Launch timeout has expired, giving up wake lock!

08-15 11:15:19.930  3100  3123 E chromium: [ERROR:gpu_watchdog_thread.cc(418)] The GPU process hung. Terminating after 10000 ms.

08-15 11:15:19.930  3100  3123 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 3123 (Watchdog)

08-15 11:15:20.033  3015  3015 W debuggerd: type=1400 audit(0.0:27): avc: denied { search } for name="org.chromium.chrome" dev="dm-0" ino=115234 scontext=u:r:debuggerd:s0 tcon