[PyQt] Android crashes

[Kálmán Viktor]

Managed to get a backtrace of sorts not sure if its any help:
https://gist.github.com/kviktor/9855e4b7b3e2df67047e089513e15977

Also slightly unrelated, but should I be able to build Python 3.6 with
pyqtdeploy v1.3.2? When I'm trying to do it I get `error: 'struct lconv'
has no member named 'decimal_point'` errors. (as I saw pyqtdeploy has
patches for 3.5.* with the HAVE_BROKEN_LOCALECONV workaround but 3.6.* has
no patch and also I recall reading somewhere that pyqtdeploy doesn't need
any patches for 3.6+ python)

2018-04-19 16:50 GMT+02:00 Phil Thompson <phil at riverbankcomputing.com>:

> On 17 Apr 2018, at 10:43 am, Kálmán Viktor <viktorvector at gmail.com> wrote:
> >
> > We have recently released our Android client in the app store and I see
> weird crashes, there is mainly 2 categories.
> >
> > One looks like this:
> > *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
> > pid: 0, tid: 0 >>> com.my.app <<<
> >
> > backtrace:
> >   #00  pc 00000000007a323c  /data/app/com.my.app-iKDbJjkEE
> JRo37MXTF-nlQ==/lib/arm/libMyapp.so (PySys_SetObject+24)
> >
> >
> >
> > The other looks like this
> > *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
> > pid: 0, tid: 0 >>> com.my.app <<<
> >
> > backtrace:
> >   #00  pc 000000000004b520  /system/lib/libc.so (tgkill+12)
> >   #01  pc 000000000001a453  /system/lib/libc.so (abort+54)
> >   #02  pc 000000000006ce5b  /data/app/com.my.aoo-cGOoB_LsJ
> lH2RTPTKYMGyw==/lib/arm/libQt5Core.so (_ZNK14QMessageLogger5fatalEPKcz+50)
> >   #03  pc 000000000034cea7  /data/app/com.my.app-cGOoB_LsJ
> lH2RTPTKYMGyw==/lib/arm/libMyapp.so
> >
> >
> > I've seen the 2nd on my development phone a few times, it usually
> happens if the app crashes and it tries to log it but it fails, about the
> PySys_SetObject I have no idea.
> >
> > Also I've noticed that both crashes have only happened on Android 8/8.1
> (tho the sample size is very small, only ~10+ crashes)
> >
> > I'm using NDK r10e, Python 3.5.3, Qt 5.9.1 (and PyQt version that was
> out that time).
> >
> > Has anyone faced similar issues before? Would upgrading to 5.9.5 and
> newer PyQt might help or just a waste of manpower?
>
> Difficult say without a more complete backtrace. Note that pyqtdeploy v2
> has dropped support for Python versions earlier that v3.6.
>
> Phil
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.riverbankcomputing.com/pipermail/pyqt/attachments/20180525/9d237f1d/attachment.html>