Not to cast aspersions on anyone's work, but there is an alternate script
editor that misbehaved in a similar way when switching between the native
editor and the alternate one. That has been ironed out some time ago, but for
the sake of historical accuracy... well... there you go.
Bob S
> O
dunbarx wrote:
> All.
> 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 ju
SE rapidly as one
develops.
I will have to pay more attention.
Aha.
Craig
-Original Message-
From: J. Landman Gay via use-livecode
To: How to use LiveCode
Cc: J. Landman Gay
Sent: Fri, Feb 21, 2020 3:24 pm
Subject: Re: Diagnosing a crasher (was Re: Quality, reputation, and improving
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 on
crasher (was Re: Quality, reputation, and improving
both)
Chiming in again since it dovetails with today's work:
Crashing bugs (and others) sometimes require a missing
factor/context/detail in the original real-world project that is tricky
to reproduce in independent test stacks. You ha
I have an IDE bug that I have to get a recipe for. It might not be possible
to whittle this one down and I might have to send Panos the full stack with
data files off line.
1) After the openCard message is passed to the engine if the script editor
is open the engine loops for 5-10 seconds before t
Chiming in again since it dovetails with today's work:
Crashing bugs (and others) sometimes require a missing
factor/context/detail in the original real-world project that is tricky
to reproduce in independent test stacks. You have to compensate for that.
I filed this crasher today, but had
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
>
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
dunbarx wrote:> Richard.
> I will keep a eye out to see if something I do or some particular
> section of code which causes a crash.
> I have no issue with sending you my stack; it is only for internal
> use. But there are many handlers in many controls on many cards, all
> in a mainStack and a h
bject: Diagnosing a crasher (was Re: Quality, reputation, and improving both)
dunbarx wrote:
> Richard wrote:
>> Crashers are of course serious, but the good news is that you're only
>> seeing it in one project. Feel free to email me directly if you're
>> in a posit
dunbarx wrote:
> Richard wrote:
>> Crashers are of course serious, but the good news is that you're only
>> seeing it in one project. Feel free to email me directly if you're
>> in a position to allow me to review the errant code, and I'll see
>> what we can do to both find a workaround to keep
12 matches
Mail list logo
