L5 - Two crashes for the price of one

Martin Folley

I have been tagging all morning, and creating bibliographies.

After several hours of use, I clicked on a bibliography to rename it .... crash.

An Apple creash report was generated (attached), which I sent to Apple after copying it.

As soon as I had sent this report, a second Apple crash report was generated, which I also copied before sending ...

Two apple crash reports, one logos crash.

1667.Apple Report.txt

0447.Apple Report 2.txt

1300.LogosLogs Martin Folley 20121124-134950.gz

Find more posts tagged with

Comments

Patrick S.

This seems pretty clearly to be a programming bug where Logos was not tracking resources properly. The application attempted to do a task accessing a file and found something wrong and bailed out.

While Logos is not running check to see if the following file:

"/Users/Martin/Library/Application Support/Logos4/Data/coqgz8dq.9ly/LibraryIndex/index.idx"

is on your system. 99% it will be - just a double check.

In Finder menu choose: Go | Go to Folder... and fill in /Users/Martin/Library/Application Support/Logos4/Data/coqgz8dq.9ly/LibraryIndex/ to go to correct folder and look for the file.

The cause of the crash is, I believe, the application not keeping track of files on disk properly.

Moral — save layouts etc. frequently while Logos irons out these bugs.

Martin Folley

https://community.logos.com/discussion/comment/430985#Comment_430985

Yes it is there ... all 5.94 Gb of it.

This is not the first instance of this file having problems under L5.

I have just restarted L5 and it has gone straight into indexing ... although I have added no new resources. The menu bar icon is reporting 'Indexing' but is not giving any % completed figure, or any indication of activity.

Activity monitor suggests that the indexer is using just 2% of CPU power. So i am not sure what it is trying to do. Whilst in Activity Monitor, i notice that L5 is using 293Mb RAM. 30 mins before the crash that had risen to 1.5 Gb ... memory leak, or resources not being unloaded? ...

I'll continue using L5 for a while and post logs later, after the indexer has had a chance to do its thing.

Patrick S.

https://community.logos.com/discussion/comment/430994#Comment_430994

Yes it is there ... all 5.94 Gb of it.

Yeah, well 6 gigs is a pretty big file....

I have just restarted L5 and it has gone straight into indexing ... although I have added no new resources. The menu bar icon is reporting 'Indexing' but is not giving any % completed figure, or any indication of activity.

Activity monitor suggests that the indexer is using just 2% of CPU power. So i am not sure what it is trying to do. Whilst in Activity Monitor, i notice that L5 is using 293Mb RAM. 30 mins before the crash that had risen to 1.5 Gb ... memory leak, or resources not being unloaded? ...

I'll continue using L5 for a while and post logs later, after the indexer has had a chance to do its thing.

I would let the indexer run — without Logos application running — until it goes away.

Memory usage, yes could be a number of things, I wouldn't exclude any of them as possibilities. Again the message to me is to save things so as to not lose work.

Martin Folley

https://community.logos.com/discussion/comment/431013#Comment_431013

I let the indexer run until it had disappeared from the menu bar .... and looking at the logs ... in an amateur way ... it looks like it crashed whist trying to merge with the idx file ...

1452.LogosLogs Martin Folley 20121124-161110.gz

Looking at the indexer folder contents ... the idx file has a modified date of the 22nd ... which ties in to the last added vyrso resource.

Martin Folley

https://community.logos.com/discussion/comment/431022#Comment_431022

Another Crash ... Another (single) Apple report.

I remember checking the RAM usage 20 minutes ago, it was either up to 1.5 or 2.5 Gb ... I cannot remember which.

I have been tagging resources, and the crash happened when pasting a resource title into the library and pressing enter.

I have added it to this thread ... I do not know if it is the same as the others above, or others that I have reported , or others that others have reported [:S] [:P]

Still loving L5 though.[:D]

4571.Apple Crash Report.txt

0160.LogosLogs Martin Folley 20121125-135602.gz

Martin Folley

https://community.logos.com/discussion/comment/431455#Comment_431455

Just a little more info ... I am generally tagging resources and making bibliographies.

I only have three items open... the library, the collections tool, and a bibliography with a single entry (I use the double click next to this to quickly create new bibliographies).

Unless by rare mistake, I do not actually open any of the resources, only tag them ...

(I am currently tagging by purchase order ... tagging by content will come later, over time).

Martin Folley

https://community.logos.com/discussion/comment/431456#Comment_431456

OK … I thought I would monitor the memory on the Logos process as I tagged. (using activity monitor to inspect the Logos thread)

I do not know if that is useful to anybody but I was curious … and surprised at the results …

Starting with Real memory Size: 581.4Mb

Paste a string into the library search … No change in memory ... resource found

Select Resource and view Info - No Change in memory use

Click on Add Tag - 0.1Mb increase as the text box opens

Type zL5 and enter --- a rapid increase in Memory usage :586 593 605 610 614 630 611.6: goes up to 630Mb before settling back down to 611.8 Mb, where it has now stabilised … a net increase of 30.4 Mb from simply adding a single tag, and not opening any additional panels or resources.

Why is it now using 30 Mb more memory? … it still has the same three windows open, and I never opened the resource itself etc.

Try again exactly the same process, exactly the same results … on adding a tag it goes up to 658.3Mb before coming down to a stable 644.4Mb A net increase of 32.6Mb this time.

Third time … goes up and then settles down at 678.4Mb. (an increase of another 34Mb).

Looking at the other memory categories this time … Virtual 1.71 Gb, Shared: 90.3, Private: 581.9, Virtual Private 712.6

The fourth time: Peaks at 729.9Mb before stabilising at 709.5 Mb (+31Mb).

The other figures have also stabilised at larger values: Virtual 1.75 Gb, Shared: 94.7, Private: 612.8, Virtual Private 743.5

Restarting Logos on my system gives these starting values: Real Memory 234.7, Virtual:1.2Gb, Shared:134.9, Private:156, Virtual Private:236.6Mb

OK ... I am not an expert ... I have not looked at memory usage since my days of 6502 assembly coding … when memory was tight and buffering for future use was unheard of … I do not know how a modern OS uses memory. I am surprised however that every tag aded is eating 30+Mb of RAM … at some point, it seems to me, you will inevitably run out of memory ...

George Somsel

I have been tagging all morning, and creating bibliographies.

After several hours of use, I clicked on a bibliography to rename it .... crash.

An Apple creash report was generated (attached), which I sent to Apple after copying it.

As soon as I had sent this report, a second Apple crash report was generated, which I also copied before sending ...

Two apple crash reports, one logos crash.

Was that a Black Friday special? [;)] Sorry to hear of your trouble.

Dave Hooton

https://community.logos.com/discussion/comment/431456#Comment_431456

Just a little more info ... I am generally tagging resources and making bibliographies.

Martin,

I take it that you are tagging resources after the indexer has crashed and you now have two problems?

Delete all the supplemental.* files in your Logos4/Data/coqgz8dq.9ly/LibraryIndex directory
Restart Logos and it will also try to build the Library Catalog Index as a result of your tagging
DON"T DO ANYTHING after you start Logos - just observe the indexer progress

If it crashes just post the logs again.

Martin Folley

https://community.logos.com/discussion/comment/431666#Comment_431666

Hi Dave.

Thanks for the suggestion.

I have been trying this for a few days now ... but having a Homer (simpson) moment ... indexing over night ... every morning the indexer icon has gone ... I start Logos with Hope ... then doh! ... it crashed ... and the logs have been deleted [:$]

I look at the new logs .. back to indexing 1 of 6532 ... it seems to regularly crash, I cannot watch it all day, and regardless of it's progress does not resume ... nor does it check the existing logs tfor a crash before deleting them ....

I am presuming that there is yet another defective resource at the heart of this (it usually is) ... but L5 indexing does not seem to handle that gracefully ... it neither skips the resource(s), or makes a note of it, nor checks the logs at startup.

Dave Hooton

https://community.logos.com/discussion/comment/433557#Comment_433557

it crashed ... anId the logs have been deleted

When Logos or the Indexer restart they overwrite the previous log. When they crash they overwrite the previous crash log, so it's important to upload logs before you start Logos again. But are you saying that there is no LogosIndexer.log nor a crash log, after a crash? If so I suggest you contact Logos Support as they can logon to your computer to diagnose the issue.

Martin Folley

https://community.logos.com/discussion/comment/433586#Comment_433586

What I was actually doing was sounding off ... at my own stupidity ... firt thing in the morning I load L5 without thinking to check the logs ...

... and at the logs not being archived automatically so that the last one is not over-written at start-up. (not kept for ever, but two versions being one the system at a time)

Whilst Posting this L5 crashed on me again ... it did not even have the focus ... I will report it in a separate thread.

Thomas Ball

https://community.logos.com/discussion/comment/431455#Comment_431455

Another Crash ... Another (single) Apple report.

I remember checking the RAM usage 20 minutes ago, it was either up to 1.5 or 2.5 Gb ... I cannot remember which.

I have been tagging resources, and the crash happened when pasting a resource title into the library and pressing enter.

I have added it to this thread ... I do not know if it is the same as the others above, or others that I have reported , or others that others have reported

Still loving L5 though.

4571.Apple Crash Report.txt

0160.LogosLogs Martin Folley 20121125-135602.gz

Are these logs from a fresh index? The logs indicating it is trying to merge which typically indicates that two separate indexes are being merged into one. if that is the case please navigate to /Users/Martin/Library/Application Support/Logos4/Data/coqgz8dq.9ly/, quit Logos 5, and move your LibraryIndex, BibleIndex, and PersonalBook Index folders to the desktop and restart Logos 5. If it still crashes there is something else in this log that has me wondering if it will be repeated, so please update the thread with those logs.

Martin Folley

https://community.logos.com/discussion/comment/440016#Comment_440016

Thanks for the reply Tommy.

I am not sure if I can do this, or rather whether it would be valid.

I am just in the process of finishing a long promised move to an SSD [:D]. I am starting afresh rather than from a Time Machine backup, and this has meant a complete download and re-index of L5. I must admit to being a little wary so I did save the log after this install (attached) ... but there were no indexing errors [<:o)].

The only error seemed to relate to not connecting with the Logos servers?

0410.LogosLogs Martin 20121209-094905.gz

Dave Hooton

https://community.logos.com/discussion/comment/440173#Comment_440173

I am not sure if I can do this, or rather whether it would be valid.

Not at this point, given you only had a communication error (fairly normal).