Re: the constant crashing of the IDE

> On 9 Oct 2015, at 11:30, J. Landman Gay wrote: > > If you're on a Mac, crash reports are saved for quite a while in Console. Thank you Jacque, it was still in there. Paul ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this

Re: the constant crashing of the IDE

I’ve added the crash log from my crash to your bug report, I suspect there may be a connection even though I was using LC8 at the time. Paul > On 9 Oct 2015, at 15:31, Dr. Hawkins wrote: > > On Fri, Oct 9, 2015 at 2:34 PM, Dr. Hawkins wrote: > >> Also, I started frequently getting the messag

Re: the constant crashing of the IDE

On Fri, Oct 9, 2015 at 2:34 PM, Dr. Hawkins wrote: > Also, I started frequently getting the message that "a stack revCursors is > already in memory". This message now *always* happens if I turn messages > off in livened before loading a stack. > now filed as *Bug 16185*

Re: the constant crashing of the IDE

On Fri, Oct 9, 2015 at 2:26 PM, Dr. Hawkins wrote: > It took an hour to rename three fields this morning . . . > Also, I started frequently getting the message that "a stack revCursors is already in memory". This message now *always* happens if I turn messages off in livened before loading a st

Re: the constant crashing of the IDE

On Fri, Oct 9, 2015 at 10:49 AM, Paul Hibbert wrote: > The same just happened to me this morning, nothing to do with messages, > but I didn’t save the crash report at the time, I can see if I can find it, > do you have a bug report for this problem? > No bug report; I don't have much to say at t

Re: the constant crashing of the IDE

If you're on a Mac, crash reports are saved for quite a while in Console. On 10/9/2015 12:49 PM, Paul Hibbert wrote: The same just happened to me this morning, nothing to do with messages, but I didn’t save the crash report at the time, I can see if I can find it, do you have a bug report for th

Re: the constant crashing of the IDE

The same just happened to me this morning, nothing to do with messages, but I didn’t save the crash report at the time, I can see if I can find it, do you have a bug report for this problem? Paul > On 9 Oct 2015, at 10:46, Dr. Hawkins wrote: > > On Fri, Oct 9, 2015 at 6:53 AM, Dr. Hawkins w

Re: the constant crashing of the IDE

On Fri, Oct 9, 2015 at 6:53 AM, Dr. Hawkins wrote: > When I get repeated crashes when saving, I try opening livecode, turning > off messages, saving, making a small number of changes, and saving again, > which usually gets me there. OK, scratch that. I just turned off messages, saved, and it b

Re: the constant crashing of the IDE

every community release onto Linux, Windows 7 and Mac OS Mavericks (VMware). Richmond. Craig Newman -Original Message- From: Dr. Hawkins To: How to use LiveCode Sent: Thu, Oct 8, 2015 9:49 pm Subject: the constant crashing of the IDE I'm seeing constant crashing of the IDE

Re: the constant crashing of the IDE

On Fri, Oct 9, 2015 at 5:35 AM, Mike Kerner wrote: > All of the crashes I have seen in the IDE have been the result of plugins - > I have *no* plugins and one library stack with scripts. I see a few crashes an hour when this is happening, the majority happening when I save. About 80% of the t

Re: the constant crashing of the IDE

man > > > > -Original Message- > From: Dr. Hawkins > To: How to use LiveCode > Sent: Thu, Oct 8, 2015 9:49 pm > Subject: the constant crashing of the IDE > > > I'm seeing constant crashing of the IDE that I can't quite reproduce. > I'm >

Re: the constant crashing of the IDE

Subject: the constant crashing of the IDE I'm seeing constant crashing of the IDE that I can't quite reproduce. I'm pretty sure that it's ore than one thing, as sometimes live code crashes while just opening a stack. But I'm starting to think I see a connect to it happeni

the constant crashing of the IDE

I'm seeing constant crashing of the IDE that I can't quite reproduce. I'm pretty sure that it's ore than one thing, as sometimes live code crashes while just opening a stack. But I'm starting to think I see a connect to it happening when a cursor has been left in a field or in an inspector. But