Crash L5 Mac

I have had a few crashed this am using L5, but each time it is different and each time I can duplicate what I was doing without the crash. It is interesting in that L5 just closes, no Apple Crash Notice with option to reopen. Because of this, unless the logs tell more than I can understand, it may be difficult to diagnose. Using MBP 2012; Mountain Lion, L5a SR1

Logs attached.4812.LogosLogs John 20121201-090055.gz

Find more posts tagged with

Comments

JT (alabama24)

You didn't have a logos.log. Can you enable logging and try again?

Hunter Clagett

You'll find full logging instructions in my signature. It would be great to get a copy of your Logos.log file.

Otherwise, feel free to call us at your convenience at 1-800-875-6467 on Monday and we'll be happy to help you resolve that issue.

Thanks,

Jack Caviness

John,

The most convenient was to enable logging is to use AppleScript application by KS4J. (Restart of Logos needed after enabling)

It appears that you already use LogosLogScribe

John Fidel

https://community.logos.com/discussion/comment/435226#Comment_435226

Thanks Jack, I have it enabled and of course no crash as it is not easy to duplicate. I am certain it is too many resources open and only occurs after hours of use. I also think that the cause is not having too many resources open, but the fact that some of the resources once open are failing to release memory. This is evidenced by the fact that after extended use L5 is using over 2 gigs of memory with a blank layout open. The layouts and resources once open and closed do not appear to be releasing memory. Fortunately I have plenty of RAM, but a less powerful machine may be exhibiting some file swap issues and slow downs.

The good news is once closed L5 will release the memory.

Hopefully this will provide enough information for Logos to diagnose and fix, at least until the next crash when I can provide more detailed logs. Hunter, thanks for your reply. If you are reading this I would be interested in your thoughts on the matter.

For test purposes, I just closed L5 Mac and reopened to a blank layout and it is only using 200 Meg of RAM. Why is there a build up of memory use over time with the opening and closing of resources? I think this and the too many resources open is directly related.

Patrick S.

https://community.logos.com/discussion/comment/435251#Comment_435251

I also think that the cause is not having too many resources open, but the fact that some of the resources once open are failing to release memory. This is evidenced by the fact that after extended use L5 is using over 2 gigs of memory with a blank layout open.

For test purposes, I just closed L5 Mac and reopened to a blank layout and it is only using 200 Meg of RAM. Why is there a build up of memory use over time with the opening and closing of resources? I think this and the too many resources open is directly related.

I would agree that this is not 'normal', certainly not desirable, system behaviour. It certainly appears that Logos 5 for Mac, as I don't believe the Windows version likely suffers this, is not releasing resources. The issue with the memory consumption is one thing, I suspect it is not releasing (properly) file 'handles' which is/may be the reason the crash report says 'too many open files'.

I would also suspect, point the finger, at the Mono layer (unique to Mac) being the culprit. Of course all this is conjecture — I just trust the Logos Mac team are giving this due diligence, it is very nasty to just have all your work blow up on you. I hope the MVPs are talking to Logos about this.

John Fidel

https://community.logos.com/discussion/comment/435272#Comment_435272

Even though there is no crash involved since my logging, I am including the logos log file for review in the even it gives a clue as to the issues discussed in my previous post.

1055.LogosLogs.gz

Anon

It is interesting in that L5 just closes, no Apple Crash Notice with option to reopen.

Noticed as of 5.0 SR4 getting unexpected quit with Apple Crash Notice. Now with 5.0a SR1 getting a lot of unexpected quitting without the Apple notice (last evening 6 without + 1 with - all within a 10 min duration).