Diagnosing a crasher (was Re: Quality, reputation, and improving both)
dunbarx at aol.com
dunbarx at aol.com
Fri Feb 21 16:36:09 EST 2020
It did just occur to me that ALL my crashes occur when the SE is open. Never just playing with the stack. I am trying to remember now whether I am modifying code or not when the crash occurs. The problem, (actually the beauty, of course) of LiveCode is that one can jump in a and out of the SE rapidly as one develops.
I will have to pay more attention.
From: J. Landman Gay via use-livecode <use-livecode at lists.runrev.com>
To: How to use LiveCode <use-livecode at lists.runrev.com>
Cc: J. Landman Gay <jacque at hyperactivesw.com>
Sent: Fri, Feb 21, 2020 3:24 pm
Subject: Re: Diagnosing a crasher (was Re: Quality, reputation, and improving both)
On 2/21/20 2:44 AM, Richard Gaskin via use-livecode wrote:
> J. Landman Gay jacque wrote:
> > We're about to submit the iOS app now and my testers have had several
> > intermittent crashes we can't repeat, even though I built that one
> > with 9.5.1 stable. I submitted crash logs but the team could only
> > repeat the problem once and there's no real recipe. How
> > would you trace something like that?
> Only iOS or in development too?
Never in the IDE, frequently in the iOS standalone, sometimes in the Android app. It seems to
depend on how long you use the app. I have never had a crash because I do unit testing and then
quit. The testers pound on it hard and they get most of the crashes because they're at it for
hours. On the other hand, my client took the Android app to a trade show and demo'ed it for 8
hours a day and never crashed. So maybe it's device-dependent? Who knows. My primary tester has
a budget Moto phone, my client has a Pixel 2. That's why I'm thinking it may be memory-related.
> I'd consider running a logger, but if it's not merely intermittent but also rare, the challenge
> is that a logger will slow things down a little bit while you're working, writing giant log
> files that most of the time aren't needed.
Both intermittent, not reproducible on demand, and never consistent. A logger would probably be
difficult to deal with on a mobile device, but more importantly, it could only tell us what
actions the user took before the crash. Since we've tried repeating the same actions many times
without any problem, there's really nothing to point a finger at.
> > It feels like a memory leak to me but that could happen anywhere in
> > the app. Wherever it is, it goes back a ways.
> How far back? In which version did you first start seeing this?
The earliest build I did was in 9.0-something but the testers never got the mobile app until I
built with 9.5.1 so I'm not sure. I should have said "goes back at least to 9.5.1."
Jacqueline Landman Gay | jacque at hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode