A27 Crash, unknown cause

Page 1 of 1 (10 items)
This post has 9 Replies | 1 Follower

Posts 1416
Wes Saad | Forum Activity | Posted: Mon, Jul 19 2010 4:55 AM

A27 froze after using it for a little while, I had to force quit. At the time that it froze, I wasn't doing anything. Noticed the spinning pizza and waited for a little bit before doing force quit. I don't see anything peculiar in the logs, but here they are anyway.

2818.Logging.zip

The following showed up in the console log:

7/19/10 6:46:29 AM [0x0-0x4e04e].com.logos.Logos_Bible_Software_4[584] 07/19/2010 06:46:29 |  INFO | 3 |     SyncManager | (Timed) Downloading items. 

7/19/10 6:46:30 AM [0x0-0x4e04e].com.logos.Logos_Bible_Software_4[584] 07/19/2010 06:46:30 |  INFO | 3 |     SyncManager | (1128ms) Downloading items. 

7/19/10 6:47:35 AM [0x0-0x4e04e].com.logos.Logos_Bible_Software_4[584] 07/19/2010 06:47:35 | DEBUG | 1 | LDLS4.Macintosh.OurApp | AppController_AttributedStringToRichText returned zero for <ResourceLink ResourceId="LLS:1.0.710" Reference="bible+esv.16.11-16.12"> 

7/19/10 6:47:35 AM [0x0-0x4e04e].com.logos.Logos_Bible_Software_4[584] 07/19/2010 06:47:35 | DEBUG | 1 | LDLS4.Macintosh.OurApp | AppController_AttributedStringToRichText returned zero for <ResourceLink ResourceId="LLS:1.0.710" Reference="bible+esv.16.13"> 

7/19/10 6:47:35 AM [0x0-0x4e04e].com.logos.Logos_Bible_Software_4[584] 07/19/2010 06:47:35 | DEBUG | 1 | LDLS4.Macintosh.OurApp | AppController_AttributedStringToRichText returned zero for <ResourceLink ResourceId="LLS:1.0.710" Reference="bible+esv.17.1-17.5"> 

7/19/10 6:47:35 AM [0x0-0x4e04e].com.logos.Logos_Bible_Software_4[584] 07/19/2010 06:47:35 | DEBUG | 1 | LDLS4.Macintosh.OurApp | AppController_AttributedStringToRichText returned zero for <ResourceLink ResourceId="LLS:1.0.710" Reference="bible+esv.20.20"> 

7/19/10 6:47:35 AM [0x0-0x4e04e].com.logos.Logos_Bible_Software_4[584] 07/19/2010 06:47:35 | DEBUG | 1 | LDLS4.Macintosh.OurApp | AppController_AttributedStringToRichText returned zero for <ResourceLink ResourceId="LLS:1.0.710" Reference="bible+esv.20.21"> 

7/19/10 6:47:35 AM [0x0-0x4e04e].com.logos.Logos_Bible_Software_4[584] 07/19/2010 06:47:35 | DEBUG | 1 | LDLS4.Macintosh.OurApp | AppController_AttributedStringToRichText returned zero for <ResourceLink ResourceId="LLS:1.0.710" Reference="bible+esv.79.4.1-79.4.13"> 

7/19/10 6:47:35 AM [0x0-0x4e04e].com.logos.Logos_Bible_Software_4[584] 07/19/2010 06:47:35 | DEBUG | 1 | ResourceDisplay | DisplayAction Leave raised for resource 'LLS:1.0.710' (IsLink: False). 

7/19/10 6:47:35 AM [0x0-0x4e04e].com.logos.Logos_Bible_Software_4[584] 07/19/2010 06:47:35 | DEBUG | 1 | ResourceDisplay | DisplayAction RichText: (null) 

7/19/10 6:48:40 AM com.apple.launchd.peruser.501[196] ([0x0-0x4e04e].com.logos.Logos_Bible_Software_4[584]) Exited: Terminated

Posts 3188
LogosEmployee
Thomas Ball | Forum Activity | Replied: Mon, Jul 19 2010 2:21 PM

If you can reproduce this could you include the Console Message.log file? The Console Message.log is important for assessment of bugs where they exist. 

 

Posts 91
Seth Hewitt | Forum Activity | Replied: Mon, Jul 19 2010 2:27 PM

Something similar to what Chris has seen.

After doing a search of my journals, and opening a number of articles (15+), the program all but stopped responding. I could scroll down a couple of lines in the article, but then the program would freeze again. I use iStat menus to monitor CPU usage and the load on a single core was 100%. This cycled between the two cores. Finally forced quit the program. The problem may have just been more resources open than the program could handle, but none were linked, and there were no windows open but the journals and the NASB95.

Logs attached

2816.Archive.zip

Moved from http://community.logos.com/forums/p/20025/150665.aspx#150665. Unable to delete post at that link.

 

Posts 91
Seth Hewitt | Forum Activity | Replied: Mon, Jul 19 2010 2:29 PM

Here's another of the same, later in the day yesterday, with not nearly so many resources open. CPU usage is very high, computer—not just L4M—becomes unusable, and eventually the program crashes.

Logs attached.

7573.Archive2.zip

Posts 3188
LogosEmployee
Thomas Ball | Forum Activity | Replied: Mon, Jul 19 2010 2:35 PM

Is this set of logs from then, or did you just now pull them?

 

Posts 91
Seth Hewitt | Forum Activity | Replied: Mon, Jul 19 2010 2:37 PM

From then. Just didn't have a chance to post yesterday. Hebrew homework and all…

Seth

Posts 3188
LogosEmployee
Thomas Ball | Forum Activity | Replied: Mon, Jul 19 2010 2:44 PM

Seth Hewitt:

Here's another of the same, later in the day yesterday, with not nearly so many resources open. CPU usage is very high, computer—not just L4M—becomes unusable, and eventually the program crashes.

Logs attached.

7573.Archive2.zip

Were your actions similar to when the first crash occurred that you reference?

 

Posts 91
Seth Hewitt | Forum Activity | Replied: Mon, Jul 19 2010 2:55 PM

Tommy,

The second time I had highlighted text in a commentary or journal (can't remember which) when I got the spinning beachball of death. I wasn't able to do anything more on the computer until L4M crashed. I wasn't doing a search, had no windows linked, nothing that would have required CPU cycles, just highlighting text. BTW, prior to both of these crashes, I was able to scroll only a few lines at a time, 4–5 at most, before having to wait on the machine to catch up. 

Posts 1416
Wes Saad | Forum Activity | Replied: Mon, Jul 19 2010 3:10 PM

Seth Hewitt:
I had highlighted text in a commentary or journal (can't remember which) when I got the spinning beachball of death.

I think it was not long after adding highlighting to a Bible that I noticed the spinning pizza.

Posts 91
Seth Hewitt | Forum Activity | Replied: Mon, Jul 19 2010 3:16 PM

To clarify, I hadn't highlighted text, I had selected it to copy. Sorry. Using "highlighting" colloquially.

S

Page 1 of 1 (10 items) | RSS