Livecode 7.1.2 too many crash

[trevix]

Using Livecode 7.1.2 (build 10052 on OS X 10.10.5 with 32 gig of Ram) I am having a number of random crashes (LC suddenly close with an error to Apple) that I believe is excessive.
I have been developing an App for the last 3 month, having at least a couple of crash a day on the developing environment.
Nothing fancy on the stacks, some data grid (but I don't thing is the issue), mostly likely a memory issue.
The Mac is healthy, packed and reinstalling LC does not change the situation.

Starting from LC 5.5.5 all the way to 7.1.2 the crashes have grown to an intolerable rate; I am feeling that the LC team has opened too many fronts and cannot make anymore a real stable release.

Anybody share this view?

[[-hh]]

If the crash is on startup, then this is a well-known issue and currently "in-work".

TMHO this is to a bigger part caused by MacOS (problem is not there, at least not frequently in MacOS < 10.10).
I use here also newest MacOS and have with LC 6/7/8 ALWAYS two trials until it starts up. I can live with that, others may not.

[Edit 2016-03-04:
LC 6.7.10-rc1 and 7.1.3-rc1 do NOT crash here on MacOS >=10.10]

MacOS 10.11 has really a big memory problem, for example Mail want's here up to 30% CPU. Ridiculous. I don't use it as main mail app any more.

-hh

[LCMark]

@trevix: I'm sorry to hear you are having this experience - we haven't had any widespread reports of crashes in 7.1.2 (or before) in the way you describe. It is quite possible that a specific thing one of your stacks is doing is exposing an unreported problem in the engine which we'd obviously like to fix! If you could take some time to file a bug report at quality.livecode.code with as much information as you can - including crash logs (you can find them in the console app) and the list of plugins you have installed - we can start a dialog to try and track down the problem. Thanks in advance!

[trevix]

I collected 26 crash in the last month.
I am not sure how to report a bug because there is not apparent clear sequence of events generating them.
As I said, they happen randomly, only after a having done intense scripting.
I attach here the reports, so that you can tell me if these are what are needed and what should I do with them.
Thanks

[trevix]

Oh My...
Like if there was a devil listening, I just pinpointed a precise sequence of events that in development mode consistently generate the dreaded error:

button "beh_DeveloperCancel": execution error at line 2652 (Handler: can't find handler) near "moveStack", char 1

and then crash LC 7.1.2 and 7.1.3

Line 2652 belongs clearly to LC, not to my stack.
When I stop the script then LC crash.

The error is generated by a Mouseup in a behavior button, something like this:

Code: Select all

on mouseUp
ClearTableSelection
end mouseUp

The button that call the behavior is in the same card where is the command "ClearTableSelection".
The behavior button is in a stack that is opened on PreOpenStack, using a

start using stack "lib_CodeNavigation"

.

Now...my stack is way to big to share (and I don't think I want to do it...)
What should I do?

[trevix]

Hi Mark.
Have you had a chance to see my reports or can you tell me a way to deal with these craches ?

Thanks

[trevix]

Anybody is willing to answer?

[FourthWorld]

Hi Mark.
Have you had a chance to see my reports or can you tell me a way to deal with these craches ?

What are the bug report numbers?

[trevix]

As I said, I have crashes without a precise sequence of events. So I don't know how to file a bug report in the LC web pages.
I thought that someone at LC could make good use of the console crash report that I uploaded.
Did i get it right?

[FourthWorld]

As I said, I have crashes without a precise sequence of events. So I don't know how to file a bug report in the LC web pages.
I thought that someone at LC could make good use of the console crash report that I uploaded.
Did i get it right?

The logs are helpful, but the forums are limited in their usefulness for bug tracking. We do see members of the core engine team here from time to time, but this is primarily a user-to-user forum so we can't rely on the engine team monitoring threads here.

This particular forum is for triaging bugs, and it would be great to see if others have experienced the same issue so they can help pin down the recipe.

But since you have crash logs and are looking to have them reviewed by the engine team, the best place to do that is in the bug database:
http://quality.livecode.com/

It's usually best to submit a bug report with a step-by-step recipe for reproducing it. If a recipe is available you'll usually find bugs fixed within just a couple days, often less.

In this case I would suggest filing the report anyway, and attaching the crash logs to it. If you later find a recipe please add it to the report, but if we're lucky the crash logs may contain enough actionable information to allow the team to identify the problem.

Please note the bug report number here after you've filed it.

[trevix]

Bug Report 17180