Logos 5 Mac Freeze

I keep having this problem where I open up a particular Saved Layout Snaphot. It's 11 tabs (4 visible) that are all linked except for two notes files. If I start scrolling around with this Layout as it's saved, it works fine.

If I type it another Bible reference, I start to have problems. The moment I try to scroll one of the panels (wheel drag or clicking on the page scroll bar to page), it freezes. Eventually, even if I don't scroll, it freezes. What this means is that Logos uses 100% of both of my CPU cores and becomes unresponsive. Memory usage does not appear to grow (and plenty is free).

I turned logging on and it doesn't print anything anywhere near the time of the freeze. But the problem is repeatable.

I have attached a stack trace with the hope that it might help. My computer is an aged MacBook Pro from 2009 (3 GHz Core 2 Duo) w/ 8 GB ram, a 512 GB SSD running OS X 10.8.3.

3884.stack.txt

Find more posts tagged with

Comments

Dave Hooton

A screen shot of the layout would be useful. To track the behaviour we would also need you to upload the logos.log from the session - see http://wiki.logos.com/Diagnostic_Logging.

Jack Caviness

I turned logging on and it doesn't print anything anywhere near the time of the freeze. But the problem is repeatable.

See the link in my signature for Logging instructions for L5 Mac

William Gabriel

https://community.logos.com/discussion/comment/496600#Comment_496600

Here's an upload of my screenshots. Top is the saved layout snapshot. Second is with the problem in progress. I've been trying several times to go to the book of Job recently and it will not come out of the freeze (even though the screen shot is from 2 Chronicles).

I will attach a log in a little bit. As I mentioned in my original post, there was nothing of note in the log, but I'll log and post it to satisfy everyone's curiosity.

William Gabriel

https://community.logos.com/discussion/comment/496611#Comment_496611

Alrighty, here are my logs. Hopefully there's something in there to help!

6888.LogosLogs.wpgabriel.20130611-173111.zip

I really appreciate this community, and I'm thankful that you're all willing to invest time to help out.

Bill

Jack Caviness

https://community.logos.com/discussion/comment/496614#Comment_496614

Alrighty, here are my logs. Hopefully there's something in there to help!

I can tell you how to collect and post them, but when it comes to reading them, I humbly bow to Dave Hooton.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/496614#Comment_496614

A screen shot of the layout would be useful.

+1 [Y] for screen shot of layout

Alrighty, here are my logs. Hopefully there's something in there to help!

LogosError.log file shows network issues connecting to Logos servers from time to time.

In Logos.log file, noticed Document sharing sync issue 4 seconds after snapshot applied, which is quickly followed by many memory allocation (malloc) errors. Looking forward to Logos insights:

06/11/2013 17:29:20 | INFO | 1 | LDLS4.AppModel | (2702ms) Applying layout snapshot. 06/11/2013 17:29:24 | INFO | 26 | DocumentManagementClient | Failed to retrieve whether document sharing can be managed online (for document with ID: 'Document:Notes:ed3556aad3884ed8972c622d6540f034') with message: Response JSON could not be deserialized to Logos.DocumentSharing.Contracts.DocumentDto: Could not find member 'actions' on object of type 'DocumentDto'. Path 'actions', line 1, position 257. Request: GET https://docapi.logos.com/v1/documents/ed3556aad3884ed8972c622d6540f034 (status OK, content type 'application/json; charset=utf-8', content length 501) 06/11/2013 17:29:24 | INFO | 7 | DocumentManagementClient | Failed to retrieve whether document sharing can be managed online (for document with ID: 'Document:Notes:1a0a924af71147ccadaab2c806cdb72b') with message: Response JSON could not be deserialized to Logos.DocumentSharing.Contracts.DocumentDto: Could not find member 'actions' on object of type 'DocumentDto'. Path 'actions', line 1, position 252. Request: GET https://docapi.logos.com/v1/documents/1a0a924af71147ccadaab2c806cdb72b (status OK, content type 'application/json; charset=utf-8', content length 496) 06/11/2013 17:29:24 | INFO | 1 | PanelLinkingManager | (Timed) Navigating requests. 06/11/2013 17:29:24 | INFO | 1 | PanelLinkingManager | (8ms) Navigating requests. Logos(12171,0xac993a28) malloc: *** error for object 0xac8ab5ac: pointer being freed was not allocated *** set a breakpoint in malloc_error_break to debug

Keep Smiling [:)]

Dave Hooton

https://community.logos.com/discussion/comment/496614#Comment_496614

Alrighty, here are my logs.

I think this is connected with the latest update of Faithlife Study Bible and an old milestone near Ro 8:28**. After you load the layout, unlink the FSB, close the tab and reload FSB (to a different reference if necessary) before linking it again.

EDIT: I would go so far as to remove the bookmarks (wear marks) in your resource margins (the 2x Show... Bookmarks options in Program Settings).

William Gabriel

https://community.logos.com/discussion/comment/496645#Comment_496645

Thanks for the help. I unlinked then closed the FSB tab. I changed the Show Bookmark options as suggested. I re-saved the layout after this at another reference (moved it to John 1).

I still get the hangup when I type in Job to the ESV tab...Looks like some of the same issues in the log. New ones uploaded.

0638.LogosLogs.wpgabriel.20130611-214350.zip

Dave Hooton

https://community.logos.com/discussion/comment/496665#Comment_496665

I note you don't load FSB in this layout, but I'll have to leave further diagnosis to Logos (you could contact them directly, referring to this thread).

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/496716#Comment_496716

... leave further diagnosis to Logos (you could contact them directly, referring to this thread).

One option is email to Logos Technical Support with reference to this thread => http://www.logos.com/contact

Keep Smiling [:)]

Mike

https://community.logos.com/discussion/comment/496665#Comment_496665

Hello William,

I apologize for the difficulty you're seeing. Per your last reply, are you typing in "Job" as in the entire book of Job? I noticed your layout contains several linked panels, including Text Comparison. Loading a layout with Text Comparison on an entire book, like "Job", is not recommended. This is going to display and search the entire book in every selected translation to show differences and "compare" the results. Even on a very fast computer, this can cause some major lag time and even hang the process.

I would recommend repeating your steps, using a smaller verse range, like "Job 1:1-5" and seeing if this is more responsive.

By limiting yourself to a verse, or few verses, your Text Comparison and any linked Guides are going to be much more responsive.

William Gabriel

https://community.logos.com/discussion/comment/496839#Comment_496839

Mike,

That seemed to do it, thanks!

Bill

Mike

https://community.logos.com/discussion/comment/497305#Comment_497305

Glad to hear it Bill.

I've submitted a report to development about this issue. We're going to try and work something out int he future to limit that report to fewer verses at a time if the reference range is too large. This should prevent accidentally entering overwhelming ranges. I don't have any ETA on this change yet, but our head of Logos Desktop Development seems to like the idea so I think it'll happen.

Jack Caviness

https://community.logos.com/discussion/comment/498059#Comment_498059

We're going to try and work something out int he future to limit that report to fewer verses at a time if the reference range is too large. This should prevent accidentally entering overwhelming ranges

Good move [Y]

William Gabriel

https://community.logos.com/discussion/comment/498059#Comment_498059

Glad to hear it Bill.

I've submitted a report to development about this issue. We're going to try and work something out int he future to limit that report to fewer verses at a time if the reference range is too large. This should prevent accidentally entering overwhelming ranges. I don't have any ETA on this change yet, but our head of Logos Desktop Development seems to like the idea so I think it'll happen.

Mike, thanks for the update. This will be a welcome change, because the problem can occur even if you don't type in too large a reference range as I had been doing.

It happened to me yesterday as I was doing some work. I was scrolling through Job, came to chapter 4, and the ESV Study Bible scrolled to a summary section with the range 4:1-25:6. I don't know if I clicked on the tab or what exactly the sequence of events was, but the Text Comparison tab picked up on this range and "froze" again. I was able to wait it out (took about 2 minutes to finish), but it's because all the panels are linked and one of the "commentary" panels had a large range that I bumped into the same issue.

For now I've unlinked the Text Comparison tab and will gladly type in a reference if I want to see one. I would suggest that the maximum number of verses allowed be user-customizable, if that's not too much extra work for development.

Thanks! Bill

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/498290#Comment_498290

I would suggest that the maximum number of verses allowed be user-customizable, if that's not too much extra work for development.

+1 [Y] so can customize number of verses for Text Comparison and number of words for Exegetical Guide.

Keep Smiling [:)]