Overthinking on Subsurface mobile app UX

[Dirk Hohndel]

> On Jun 22, 2017, at 1:33 AM, Davide DB <dbdavide at gmail.com> wrote:
>> 
>> I have not seen this in a long time. Can you connect to the phone from a
>> computer with adb and check what it says in the logcat? Is it possible
>> that we are running out of memory?
> 
> I have three phones: Nexus 5x, Huwaei P7 and a LG Xpower. I get an
> error dialog  "unfortunately Subsurface has stopped" on exit only on
> the LG.

Let's ask some simple questions about what's different with the LG:
a) which Android versions are the three devices running?
b) how much RAM do they have?

> I installed ADB and I was able to grab some log while running
> Subsurface. I'm new to this so I was able to filter only for Error
> category.
> 
> adb logcat *:E

I usually pull the whole logcat (unfiltered) into a file, then search
for the crash (SIGSEGV in your case) and then look at all the
messages in the few moments before.

> If you need something more specific, please guide me into the folds fo ADB.
> 
> This is what I get on exit:
> 
> 
> 06-22 10:22:54.150 28930 28954 F libc    : Fatal signal 11 (SIGSEGV),
> code 1, fault addr 0x18 in tid 28954 (QtThread)
> 06-22 10:22:54.204 28973 28973 F AEE/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
> 06-22 10:22:54.204 28973 28973 F AEE/DEBUG: Build fingerprint: 'lge/mk6pn_global_com/mk6pn:6.0.1/MXB48T/1620123115f06:user/release-keys'
> 06-22 10:22:54.205 28973 28973 F AEE/DEBUG: Revision: '1.0'
> 06-22 10:22:54.205 28973 28973 F AEE/DEBUG: ABI: 'arm'
> 06-22 10:22:54.205 28973 28973 F AEE/DEBUG: pid: 28930, tid: 28954, name: QtThread  >>> org.subsurfacedivelog.mobile <<<
> 06-22 10:22:54.205 28973 28973 F AEE/DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x18
> 06-22 10:22:54.252 28973 28973 F AEE/DEBUG:     r0 b8320098  r1 00000000  r2 2e10f7e6  r3 00000018
> 06-22 10:22:54.252 28973 28973 F AEE/DEBUG:     r4 b82d9e68  r5 b82d9e68  r6 b833dfa0  r7 b6ca2e40
> 06-22 10:22:54.252 28973 28973 F AEE/DEBUG:     r8 b847d0f0  r9 b82d9e68  sl 00000001  fp b847cab0
> 06-22 10:22:54.252 28973 28973 F AEE/DEBUG:     ip 9d342004  sp 9b7fbe48  lr 9d24202f  pc 00000018  cpsr 600b0010
> 06-22 10:22:54.253 28973 28973 F AEE/DEBUG:
> 06-22 10:22:54.253 28973 28973 F AEE/DEBUG: backtrace:
> 06-22 10:22:54.253 28973 28973 F AEE/DEBUG:     #00 pc 00000018  <unknown>
> 06-22 10:22:54.253 28973 28973 F AEE/DEBUG:     #01 pc 0011602d /data/app/org.subsurfacedivelog.mobile-2/lib/arm/libQt5Quick.so (_ZNK12QQuickWindow16mouseGrabberItemEv+56)
> 06-22 10:22:54.790 28973 28973 E AEE/AED : request.action: 0
> 06-22 10:22:54.826   314   314 E lowmemorykiller: Error writing /proc/28930/oom_score_adj; errno=22

That last one "lowmemorykiller" makes me wonder about question b) above

/D