Message Tracer/IDE Crash Recipes

[Craig Newman]

Curry.

It always happens in the IDE when I am working on my largest desktop project, an eight year old mainStack that contains six substacks. I work on that project only on my main office computer. Invariably I am fooling around between the SE and the mainStack.

It has never happened when I am working on any other stack. I never work on that particular project on any other machine I use, and have never had a crash on any of those others.

So it is limited to one machine and one project. I do have a large second monitor oriented vertically that holds only the SE. I use no fancy stuff, no databases, dataGrids, external files. I use one plug-in that contains a few shortcuts, like being able to right-click and switch between the browse and pointer tool. 

The project will run fine for months, in constant use, but then crash. Not reproducible as far as I can tell.

Craig

> On Oct 28, 2021, at 9:01 PM, Curry Kenworthy via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> 
> Craig:
> 
> > My one entry into the "bug” poll was to complain
> > about random crashes of LC itself now and then.
> > Not likely to have that solved anytime soon.
> 
> It could be! There is de-crashing LC progress, but it's slow.
> This year I reported a crash/hang pair, and that's fixed now.
> 
> The problem is a solid recipe, as I'm sure you know.
> Searching for "crash" in quality.livecode.com
> reveals a bunch of AWAITING_FOLLOW_UP and NOT_REPRODUCED.
> 
> For a bug that is unusually difficult to recipe,
> it requires collaboration (or etc) to pin it down.
> That in turn requires some ... discussion.
> 
> (Encouraging that discussion would be in LC's own interest;
> customers put a lot of unpaid hard work into bug filing efforts.)
> 
> I'm taking a rare opportunity to catch up here on the list
> after finally getting over COVID (man, it feels good!)
> but must dive back into my own client work and addons updates.
> 
> However, LC bugs impact both client work and addons updates too,
> so it's all related. LC bug time is mandatory either way!
> There's no getting around it.
> 
> The survey made me realize I need better LC bug tracking tools,
> so I can stay on top of the old and new ones, plus rank them.
> And follow up on any reports that have lapsed.
> 
> So I'm curious: Craig, what was the nature of your crash?
> (Or the bug # / discussion link, if that applies.)
> I'll keep it in mind, to see if I can help eventually
> with the pesky recipes or crash log data.
> May take a while, but we can pin down more of these.
> 
> Best wishes,
> 
> Curry Kenworthy
> 
> Custom Software Development
> "Better Methods, Better Results"
> Christian LiveCode Training and Consulting
> http://livecodeconsulting.com/
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode