Discussion:
[Interest] lib houdini crash
Nuno Santos
2015-03-20 12:41:38 UTC
Permalink
Hi,

It seems that Qt based Android apps are crashing on Intel based devices. Is anyone else experiencing the same problem?

Regards,

Nuno

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/santos10wifixx/santos10wifi:4.4.2/KOT49H/P5210XXUBNK2:user/release-keys'
Revision: '0'
pid: 16815, tid: 16835, name: m.imaginando.lk >>> com.imaginando.lk <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000049
eax 00000000 ebx 00000049 ecx 00000048 edx 1a215030
esi 1a215030 edi 00000005
xcs 00000073 xds 0000007b xes 0000007b xfs 00000043 xss 0000007b
eip 64b22283 ebp 661cdbbc esp 661cdba4 flags 00210246

backtrace:
#00 pc 000af283 /system/lib/libhoudini.so
#01 pc 0010202f [stack:16834]
#02 pc 000c918e /system/lib/libhoudini.so
#03 pc 0000e72f <unknown>
#04 pc 000b2247 /system/lib/libhoudini.so
#05 pc 0010202f [stack:16834]
#06 pc 000aeea7 /system/lib/libhoudini.so
#07 pc 000a3377 /data/app-lib/com.imaginando.lk-1/libQt5Gui.so
#08 pc 000aefdc /system/lib/libhoudini.so
#09 pc 00244a48 /data/app-lib/com.imaginando.lk-1/libQt5Gui.so
#10 pc 0018460b /system/lib/libhoudini.so
#11 pc 00024a4a /data/data/com.imaginando.lk/qt-reserved-files/plugins/platforms/android/libqtforandroid.so
#12 pc 00181bdc /system/lib/libhoudini.so
#13 pc 00052da8 <unknown>
#14 pc 000ffd1f [stack:16835]
Nuno Santos
2015-03-20 13:31:05 UTC
Permalink
Ministro is the default option. Is this the recommend way of doing it?

I really don't understand my options here.

When you say x86, do you mean android x86?

I didn't even have that installed.

--
Nuno Santos
Hello,
If you're using ministro make sure your app is compiled with x86 and not arm.
Post by Nuno Santos
Hi,
It seems that Qt based Android apps are crashing on Intel based
devices. Is anyone else experiencing the same problem?
Regards,
Nuno
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
'samsung/santos10wifixx/santos10wifi:4.4.2/KOT49H/P5210XXUBNK2:user/release-keys'
Revision: '0'
pid: 16815, tid: 16835, name: m.imaginando.lk >>> com.imaginando.lk <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000049
eax 00000000 ebx 00000049 ecx 00000048 edx 1a215030
esi 1a215030 edi 00000005
xcs 00000073 xds 0000007b xes 0000007b xfs 00000043 xss 0000007b
eip 64b22283 ebp 661cdbbc esp 661cdba4 flags 00210246
#00 pc 000af283 /system/lib/libhoudini.so
#01 pc 0010202f [stack:16834]
#02 pc 000c918e /system/lib/libhoudini.so
#03 pc 0000e72f <unknown>
#04 pc 000b2247 /system/lib/libhoudini.so
#05 pc 0010202f [stack:16834]
#06 pc 000aeea7 /system/lib/libhoudini.so
#07 pc 000a3377 /data/app-lib/com.imaginando.lk-1/libQt5Gui.so
#08 pc 000aefdc /system/lib/libhoudini.so
#09 pc 00244a48 /data/app-lib/com.imaginando.lk-1/libQt5Gui.so
#10 pc 0018460b /system/lib/libhoudini.so
#11 pc 00024a4a
/data/data/com.imaginando.lk/qt-reserved-files/plugins/platforms/android/libqtforandroid.so
#12 pc 00181bdc /system/lib/libhoudini.so
#13 pc 00052da8 <unknown>
#14 pc 000ffd1f [stack:16835]
_______________________________________________
Interest mailing list
http://lists.qt-project.org/mailman/listinfo/interest
Harri Pasanen
2015-03-20 18:45:48 UTC
Permalink
Crashing how, all the time in same place, or sometimes?

As for me, I'm providing both x86 and arm apk to Play Store for Stoppola.

The arm alone does work, because Android on Intel does binary
translation, but is a bit slower especially at startup.

Also for video encoding the native intel build is about 4x faster than
the arm running on Intel. So for some tasks you definitely want native
builds.

As to crashing, I don't have hard data, but a gut feeling that arm on
Intel might have seen some unexpected crashes. Might have been just a
coincidence though.

Regards,

Harri
Post by Nuno Santos
Hi,
It seems that Qt based Android apps are crashing on Intel based devices. Is anyone else experiencing the same problem?
Regards,
Nuno
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/santos10wifixx/santos10wifi:4.4.2/KOT49H/P5210XXUBNK2:user/release-keys'
Revision: '0'
pid: 16815, tid: 16835, name: m.imaginando.lk >>> com.imaginando.lk <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000049
eax 00000000 ebx 00000049 ecx 00000048 edx 1a215030
esi 1a215030 edi 00000005
xcs 00000073 xds 0000007b xes 0000007b xfs 00000043 xss 0000007b
eip 64b22283 ebp 661cdbbc esp 661cdba4 flags 00210246
#00 pc 000af283 /system/lib/libhoudini.so
#01 pc 0010202f [stack:16834]
#02 pc 000c918e /system/lib/libhoudini.so
#03 pc 0000e72f <unknown>
#04 pc 000b2247 /system/lib/libhoudini.so
#05 pc 0010202f [stack:16834]
#06 pc 000aeea7 /system/lib/libhoudini.so
#07 pc 000a3377 /data/app-lib/com.imaginando.lk-1/libQt5Gui.so
#08 pc 000aefdc /system/lib/libhoudini.so
#09 pc 00244a48 /data/app-lib/com.imaginando.lk-1/libQt5Gui.so
#10 pc 0018460b /system/lib/libhoudini.so
#11 pc 00024a4a /data/data/com.imaginando.lk/qt-reserved-files/plugins/platforms/android/libqtforandroid.so
#12 pc 00181bdc /system/lib/libhoudini.so
#13 pc 00052da8 <unknown>
#14 pc 000ffd1f [stack:16835]
_______________________________________________
Interest mailing list
http://lists.qt-project.org/mailman/listinfo/interest
Thiago Macieira
2015-03-20 19:17:44 UTC
Permalink
Post by Nuno Santos
Hi,
It seems that Qt based Android apps are crashing on Intel based devices. Is
anyone else experiencing the same problem?
Why are you trying to run ARM binaries on x86? Simply compile for x86.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Nuno Santos
2015-03-20 19:40:27 UTC
Permalink
I'm not running. This is what I receive from google crash reports.

--
Nuno Santos
Post by Thiago Macieira
Post by Nuno Santos
Hi,
It seems that Qt based Android apps are crashing on Intel based devices. Is
anyone else experiencing the same problem?
Why are you trying to run ARM binaries on x86? Simply compile for x86.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
_______________________________________________
Interest mailing list
http://lists.qt-project.org/mailman/listinfo/interest
Thiago Macieira
2015-03-21 18:15:11 UTC
Permalink
Post by Nuno Santos
I'm not running. This is what I receive from google crash reports.
Then you're making your users run ARM binaries on x86. Compile your
application for x86 too and upload it to google.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Nuno Santos
2015-03-24 11:23:39 UTC
Permalink
Should I compile my app for armv5, armv7 and x86 and upload all the APK’s?

I’m currently deploying for armv7 only.

I have people telling me that the app crashes during startup without any kind of indication and I can’t tell what is exactly is causing the crash.
Post by Thiago Macieira
Post by Nuno Santos
I'm not running. This is what I receive from google crash reports.
Then you're making your users run ARM binaries on x86. Compile your
application for x86 too and upload it to google.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
_______________________________________________
Interest mailing list
http://lists.qt-project.org/mailman/listinfo/interest
Harri Pasanen
2015-03-24 11:31:22 UTC
Permalink
Forget about armv5, those devices are low on memory and cheap, but any
bad performance will still be attributed to you app and result in bad
reviews.

So build for armv7 and x86. The latter should have the same version
name, but higher version code. That way the x86 device will load the
x86 apk and not the arm one.
(if the arm apk has a higher version code, it will be loaded also to x86
devices, so don't do that.)

Hope this helps,

Harri
Post by Nuno Santos
Should I compile my app for armv5, armv7 and x86 and upload all the APK’s?
I’m currently deploying for armv7 only.
I have people telling me that the app crashes during startup without any kind of indication and I can’t tell what is exactly is causing the crash.
Post by Thiago Macieira
Post by Nuno Santos
I'm not running. This is what I receive from google crash reports.
Then you're making your users run ARM binaries on x86. Compile your
application for x86 too and upload it to google.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
_______________________________________________
Interest mailing list
http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
http://lists.qt-project.org/mailman/listinfo/interest
Nuno Santos
2015-03-24 11:34:39 UTC
Permalink
Thanks for the insights!

Regards,

Nuno
Post by Harri Pasanen
Forget about armv5, those devices are low on memory and cheap, but any
bad performance will still be attributed to you app and result in bad
reviews.
So build for armv7 and x86. The latter should have the same version
name, but higher version code. That way the x86 device will load the
x86 apk and not the arm one.
(if the arm apk has a higher version code, it will be loaded also to x86
devices, so don't do that.)
Hope this helps,
Harri
Post by Nuno Santos
Should I compile my app for armv5, armv7 and x86 and upload all the APK’s?
I’m currently deploying for armv7 only.
I have people telling me that the app crashes during startup without any kind of indication and I can’t tell what is exactly is causing the crash.
Post by Thiago Macieira
Post by Nuno Santos
I'm not running. This is what I receive from google crash reports.
Then you're making your users run ARM binaries on x86. Compile your
application for x86 too and upload it to google.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
_______________________________________________
Interest mailing list
http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
http://lists.qt-project.org/mailman/listinfo/interest
Nuno Santos
2015-03-24 11:43:55 UTC
Permalink
Quick question


In this specific case i’m trying to find more about the crash. The chip is a Rockchip RK2906

http://www.cnx-software.com/2012/08/18/60-rockchip-rk2906-cortex-a8-android-4-0-tablets/ <http://www.cnx-software.com/2012/08/18/60-rockchip-rk2906-cortex-a8-android-4-0-tablets/>

What kind of arm version is this? Can’t find that info anywhere. Probably I don’t know what search for.

Regards,

Nuno
Post by Nuno Santos
Thanks for the insights!
Regards,
Nuno
Post by Harri Pasanen
Forget about armv5, those devices are low on memory and cheap, but any
bad performance will still be attributed to you app and result in bad
reviews.
So build for armv7 and x86. The latter should have the same version
name, but higher version code. That way the x86 device will load the
x86 apk and not the arm one.
(if the arm apk has a higher version code, it will be loaded also to x86
devices, so don't do that.)
Hope this helps,
Harri
Should I compile my app for armv5, armv7 and x86 and upload all the APK’s?
I’m currently deploying for armv7 only.
I have people telling me that the app crashes during startup without any kind of indication and I can’t tell what is exactly is causing the crash.
Post by Thiago Macieira
Post by Nuno Santos
I'm not running. This is what I receive from google crash reports.
Then you're making your users run ARM binaries on x86. Compile your
application for x86 too and upload it to google.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
_______________________________________________
Interest mailing list
http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
http://lists.qt-project.org/mailman/listinfo/interest
Thiago Macieira
2015-03-24 15:50:47 UTC
Permalink
Quick question…
In this specific case i’m trying to find more about the crash. The chip is a
Rockchip RK2906
libhoudini won't be running on a Rockchip. That's an Intel proprietary library
that emulates ARM so that you can run ARM NDK apps on your x86 Android
applications.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Thiago Macieira
2015-03-24 18:17:31 UTC
Permalink
Post by Thiago Macieira
libhoudini won't be running on a Rockchip. That's an Intel proprietary
library that emulates ARM so that you can run ARM NDK apps on your x86
Android applications.
On your x86 Android device, I mean.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Nuno Santos
2015-03-24 18:25:01 UTC
Permalink
Thiago,

Didn’t even notice! ;)
Post by Thiago Macieira
Post by Thiago Macieira
libhoudini won't be running on a Rockchip. That's an Intel proprietary
library that emulates ARM so that you can run ARM NDK apps on your x86
Android applications.
On your x86 Android device, I mean.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
_______________________________________________
Interest mailing list
http://lists.qt-project.org/mailman/listinfo/interest
Thiago Macieira
2015-03-24 15:49:25 UTC
Permalink
Post by Nuno Santos
Should I compile my app for armv5, armv7 and x86 and upload all the APK’s?
Yes, and x86-64 too, these days.
Post by Nuno Santos
I’m currently deploying for armv7 only.
I have people telling me that the app crashes during startup without any
kind of indication and I can’t tell what is exactly is causing the crash.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Loading...