Perpetual Crashes: 5.2a SR-1 (on Mac)

This is somewhat similar to the crashes here with errors on the Athelas Logos NSFont, but the crash is very different; "Too many open files" in a few different scenarios. This may have to be resolved with Tech Support.

You have some very inefficient Library Catalog filters (probably used in collections).

Try changing "a, e, i, o, u ANDNOT type:bible ANDNOT type:commentary ANDNOT type:lectionary" to "* ANDNOT type:bible ANDNOT type:commentary ANDNOT type:lectionary"

Similarly, change "a, e, i, o, u ANDNOT perseus ANDNOT type:Bible ANDNOT type:commentary ANDNOT type:lectionary" to "* ANDNOT perseus ANDNOT type:Bible ANDNOT type:commentary ANDNOT type:lectionary"

(There may be other collections that use "a, e, i, o, u"; change them all to use "*".)

Make sure to use quotes around field values that are more than one word. E.g., change
author:Raymond E. Brown
to
author:"Raymond E. Brown"

Change
Author:R.C. Sproul
to
author:"R.C. Sproul"

There may be other collections that can be improved, but are lost in the noise of the current log. After you've made these changes, post another Logos.log and we can take a look.

https://community.logos.com/discussion/comment/587365#Comment_587365

After you've made these changes, post another Logos.log and we can take a look.

Thanks for your help with this, Bradley. It is much appreciated.

I have made the changes highlighted above (plus a couple of other inefficiencies). Please see new logs attached.

1055.LogosLogs.ae.20140421-170350.zip

Thomas Ball

https://community.logos.com/discussion/comment/587389#Comment_587389

HI Andy,

The newest logs don't display a crash. Were they supposed to?

https://community.logos.com/discussion/comment/587389#Comment_587389

Is it still crashing, or were you just asking for additional help with Collections queries? (I didn't see a crash in this second set of logs.)

There are a handful of queries that seem to be expensive (they all have a long list of different authors' names), but I can't reproduce the same slowdowns shown in your log on my Windows workstation.

I suspect that some of the duplicate work shown in your log (which will be slowing your system down) may be caused by opening to a complex layout, rather than a blank workspace. I further suspect, but don't know for sure, that Comparison Tool may be causing the bulk of the problems. You may wish to try recreating your startup layout without Comparison Tool, to see if that helps.

We'll also look into making sure the system doesn't do the same work twice (unnecessarily) when multiple components are being initialised during startup.

https://community.logos.com/discussion/comment/587435#Comment_587435

The newest logs don't display a crash. Were they supposed to?

L5 did not crash during operation, but, on start up, I received the following message,

I get this same message every time on restart. I have shut down L5, restarted and then shut down again before extracting the logs (in an attempt to capture the crash). I have attached this new log file. For clarity, this is not a huge deal for me (it is barely inconvenient). The random crashes when working in L5 seem now to have gone (which was my main issue). Please let me know if you need me to post anything further.

4682.LogosLogs.ae01.20140421-201754.zip

I suspect that some of the duplicate work shown in your log (which will be slowing your system down) may be caused by opening to a complex layout, rather than a blank workspace. I further suspect, but don't know for sure, that Comparison Tool may be causing the bulk of the problems. You may wish to try recreating your startup layout without Comparison Tool, to see if that helps.

Thanks for this, Bradley. It is an unusually complex layout for a very specific piece of work. I will simplify henceforth. Thank you also for the tip regarding the Comparison Tool. That is very easy for me to exclude for the moment.

We'll also look into making sure the system doesn't do the same work twice (unnecessarily) when multiple components are being initialised during startup.

Thank you for this (and your assistance generally). It is much appreciated.

https://community.logos.com/discussion/comment/587436#Comment_587436

We'll also look into making sure the system doesn't do the same work twic

But why do the 'invalid' NSFont messages arise, as with the other case I referred to?

https://community.logos.com/discussion/comment/587445#Comment_587445

4682.LogosLogs.ae01.20140421-201754.zip

I am concerned about the Indexer (Indexer.log) which detected a lot of resources in the /Downloaded folder but did nothing! Whilst I don't recognise most of them the macartsb.lbxlls is superceded by macartsb.logos4. It checks if version '2003-06-24T21:46:46Z' is available when the current version is 2013-08-12T15:23:18Z (macartsb.logos4). You might check if you have the latest version. But I would delete the /Users/andrewevans/Library/Application Support/Logos4/Data/4y4n0xc0.la9/ResourceManager/Downloaded folder as it should be empty.

https://community.logos.com/discussion/comment/587445#Comment_587445

I get this same message every time on restart.

If you get this message every time on startup (when the program didn't actually crash), it sounds like you might be running into a bug previously reported here: http://community.logos.com/forums/t/83533.aspx. I think you may be able to suppress it for now by deleting the crash report files in ~/Library/Logs/DiagnosticReports/

https://community.logos.com/discussion/comment/587492#Comment_587492

But why do the 'invalid' NSFont messages arise, as with the other case I referred to?

No idea, sorry.

https://community.logos.com/discussion/comment/587515#Comment_587515

But why do the 'invalid' NSFont messages arise, as with the other case I referred to?

No idea, sorry.

I hope it is being investigated, then.

Thomas Ball

https://community.logos.com/discussion/comment/587644#Comment_587644

Andy,

If you're concerned about those error messages related to your font can you check for bad fonts? The output should look like this if there is a bad font:

MacFontTest Error Example:

Checking CappioExtrafrisky
  display name: CappioExtrafrisky
Checking Cardigan
  display name: Cardigan
Checking Caricature
  display name: Caricature
Checking Carolus Roman
Bus error: 10
——
In this case, “Carolus Roman” was corrupt and needed to be removed.

https://community.logos.com/discussion/comment/587514#Comment_587514

I think you may be able to suppress it for now by deleting the crash report files in ~/Library/Logs/DiagnosticReports/

Thanks, Bradley, that worked.

If you're concerned about those error messages related to your font can you check for bad fonts?

Thanks, Tommy. Just to feedback, I ran the script and no errors were detected.

https://community.logos.com/discussion/comment/587825#Comment_587825

Thanks, Tommy. Just to feedback, I ran the script and no errors were detected.

Except for the numerous error messages produced by Logos!

https://community.logos.com/discussion/comment/587500#Comment_587500

I am concerned about the Indexer (Indexer.log) which detected a lot of resources in the /Downloaded folder but did nothing! Whilst I don't recognise most of them the macartsb.lbxlls is superceded by macartsb.logos4. It checks if version '2003-06-24T21:46:46Z' is available when the current version is 2013-08-12T15:23:18Z (macartsb.logos4). You might check if you have the latest version. But I would delete the /Users/andrewevans/Library/Application Support/Logos4/Data/4y4n0xc0.la9/ResourceManager/Downloaded folder as it should be empty.

Andy, have you looked at this?

https://community.logos.com/discussion/comment/587886#Comment_587886

I am concerned about the Indexer (Indexer.log) which detected a lot of resources in the /Downloaded folder but did nothing! Whilst I don't recognise most of them the macartsb.lbxlls is superceded by macartsb.logos4. It checks if version '2003-06-24T21:46:46Z' is available when the current version is 2013-08-12T15:23:18Z (macartsb.logos4). You might check if you have the latest version. But I would delete the /Users/andrewevans/Library/Application Support/Logos4/Data/4y4n0xc0.la9/ResourceManager/Downloaded folder as it should be empty.

Andy, have you looked at this?

Apologies, Dave, I missed your original advice (I think we are in different timezones!).

For clarity, do I delete the entire folder or just the contents?