Diagnosing a crasher (was Re: Quality, reputation, and improving both)

[J. Landman Gay]

I'm having the same problem. I had to build with the latest 9.6dp release 
because it fixed some Android issues and I had a deadline. It's in the Play 
Store now and it's had several crashes and ANRS. There's no info on the 
cause and we couldn't repeat it. 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?

It feels like a memory leak to me but that could happen anywhere in the 
app. Wherever it is, it goes back a ways.
--
Jacqueline Landman Gay | jacque at hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On February 20, 2020 10:40:59 PM dunbarx--- via use-livecode 
<use-livecode at lists.runrev.com> wrote:

> So I am fascinated; how would you even start? It isn't one handler that 
> causes the problem.