Latest subsurface-mobile craches on android

[Dirk Hohndel]

> On Apr 12, 2017, at 12:04 PM, Jan Van Winkel <vanwinkeljan at gmail.com> wrote:
> 
> Dirk,
> 
> As promised (see mail thread: IOS Subsurface-mobile) the logs from the crash during startup, looks like a seg fault.
> This crash is seen on a Moto G4 Play, Android 6.0.1
> 
> Output  of adb logcat -s Subsurface,DEBUG,libc:
> 
> 04-12 20:33:24.434  5848  5872 W Subsurface: (null):0 ((null)): QFont::setPointSizeF: Point size <= 0 (-1.000000), must be greater than 0
> 04-12 20:33:24.940  5848  5872 D Subsurface: (null):0 ((null)): Starting "Subsurface-mobile:1.2.1(4.6.3.215):Android 6.0.1:arm:en-US"
> 04-12 20:33:24.941  5848  5872 D Subsurface: (null):0 ((null)): "build with Qt Version 5.8.0, runtime from Qt Version 5.8.0"
> 04-12 20:33:24.944  5848  5872 D Subsurface: (null):0 ((null)): "Created position source android"
> 04-12 20:33:24.944  5848  5872 D Subsurface: (null):0 ((null)): location service is available
> 04-12 20:33:25.821  5848  5872 W Subsurface: (null):0 ((null)): Both point size and pixel size set. Using pixel size.
> 04-12 20:33:25.892  5848  5872 W Subsurface: qrc:/Icon.qml:35 ((null)): qrc:/Icon.qml:35:5: QML Image: Cannot open: qrc:/icons/go-up.svg
> 04-12 20:33:26.409  5848  5872 W Subsurface: :-1 ((null)): <Unknown File>: QML QQuickLayoutAttached: Binding loop detected for property "rightMargin"
> 04-12 20:33:26.411  5848  5872 W Subsurface: (null):0 ((null)): Both point size and pixel size set. Using pixel size.
> 04-12 20:33:26.414  5848  5872 D Subsurface: qrc:///qml/main.qml:48 (onCompleted): qml: Reduce font size for narrow screens: 10.666666666666666
> 04-12 20:33:26.652  5848  5872 D Subsurface: qrc:///qml/main.qml:279 (onCompleted): qml: [object Object]
> 04-12 20:33:26.653  5848  5872 W Subsurface: qrc:/templates/ApplicationHeader.qml:123 ((null)): qrc:/templates/ApplicationHeader.qml:123: TypeError: Cannot read property of null
> 04-12 20:33:27.282  5848  5872 D Subsurface: (null):0 ((null)): qqwindow devicePixelRatio 2 2
> 04-12 20:33:27.283  5848  5872 D Subsurface: (null):0 ((null)): qqwindow screen has ldpi/pdpi 72 147.452
> 04-12 20:33:27.288  5848  5872 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x34 in tid 5872 (QtThread)
> 04-12 20:33:27.395  4715  4715 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
> 04-12 20:33:27.395  4715  4715 F DEBUG   : Build fingerprint: 'motorola/harpia/harpia:6.0.1/MPIS24.241-15.3-16/17:user/release-keys'
> 04-12 20:33:27.395  4715  4715 F DEBUG   : Revision: 'p1b0'
> 04-12 20:33:27.395  4715  4715 F DEBUG   : ABI: 'arm'
> 04-12 20:33:27.395  4715  4715 F DEBUG   : pid: 5848, tid: 5872, name: QtThread  >>> org.subsurfacedivelog.mobile <<<
> 04-12 20:33:27.396  4715  4715 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x34
> 04-12 20:33:27.432  4715  4715 F DEBUG   :     r0 b9a2c2b8  r1 0000000c  r2 00000010  r3 00000000
> 04-12 20:33:27.433  4715  4715 F DEBUG   :     r4 b9a2e988  r5 b9a2e928  r6 b9a44288  r7 b6cdde40
> 04-12 20:33:27.433  4715  4715 F DEBUG   :     r8 a1b92e40  r9 b9a2e9d0  sl b9a442ac  fp b9a302f0
> 04-12 20:33:27.433  4715  4715 F DEBUG   :     ip 00000000  sp a1b92e40  lr a395c193  pc a395c19c  cpsr 800f0030
> 04-12 20:33:27.434  4715  4715 F DEBUG   :
> 04-12 20:33:27.434  4715  4715 F DEBUG   : backtrace:
> 04-12 20:33:27.434  4715  4715 F DEBUG   :     #00 pc 0010119c  /data/app/org.subsurfacedivelog.mobile-2/lib/arm/libQt5Quick.so (_ZN10QQuickItemD2Ev+143)
> 04-12 20:33:27.434  4715  4715 F DEBUG   :     #01 pc 0010118f  /data/app/org.subsurfacedivelog.mobile-2/lib/arm/libQt5Quick.so (_ZN10QQuickItemD2Ev+130)
> 04-12 20:33:27.868  4715  4715 F DEBUG   :
> 04-12 20:33:27.868  4715  4715 F DEBUG   : Tombstone written to: /data/tombstones/tombstone_06
> 04-12 20:33:27.868  4715  4715 E DEBUG   : AM write failed: Broken pipe
> 

OK, so this dies in the QQuickItem destructor. That's a starting point.

Now I need to figure out which of our objects are derived from that and what we are destroying twice...

/D