Crash while trying to develop a Handout

Repeated crashes today while trying to develop a handout for my Small Group meeting tomorrow on John 8: 31-59.

Using version 4.2 SR-2 (4.20.4.8828).

Logos 4 is stable enough with other things, and previous builds have not had any trouble with Handouts, although I have not used the "handouts" feature since preparing for my Dec 8th meeting late last year.

Out of memory per the Crash Log does not make sense to me : system was just restarted and has nothing much else running and plenty of memory and free disc space.

Logs attached.

46080.Logos4.log

8420.Logos4Crash.txt

4135.Logos4Indexer.log

Find more posts tagged with

Comments

David Wilson

Another crash today on my backup computer which uses Windows Vista 64 bit rather than Windows 7 : this time I was only trying to read a commentary on the John 8:31-59 passage .....

7357.Logos4Crash.txt

any ideas ?

TCBlack

https://community.logos.com/discussion/comment/225946#Comment_225946

Hmm. It seems a bit odd that despite having 6GB / 8GB of RAM you're getting out of memory errors.

Hopefully someone better able to read logs will be along in a minute.

TCBlack

https://community.logos.com/discussion/comment/225946#Comment_225946

Any chance we could get the logos4.log from the second computer?

David Wilson

https://community.logos.com/discussion/comment/225962#Comment_225962

Did not have logs enabled on the second computer for its crash and now that I have them enabled I have not yet been able to reproduce the crash (given I am trying to stay away from the handouts as I was not using them prior to the crash on the second computer).

My suspicions at this point are related to the "Classic" handout format, which is what I was using on the first computer for the John 8:31-59 passage. I was subsequently able to assemble what I wanted in a handout by sticking with the default "thin" format.

The crash on the second computer "might" have been related to its synching and downloading the Classic Format handout which is now of course part of "My Content".

David Wilson

https://community.logos.com/discussion/comment/226057#Comment_226057

An additional oddity is that because I had already assembled a Classic format handout on this passage John 8:31-59, that when I tried the workaround to create another using the default Thin format, the second one was named John 8:31–59 (2) and the (2) is stuck in there as if it were part of the passage reference. While you can nominally edit this text to remove the (2), it appears I am not going to be able to remove the (2) without first renaming the first handout (Classic format) to something else (which I cannot do as attempts to open it crash Logos 4). Interesting.....

David Wilson

This crash continues to occur when I try to do a search on John 8: 31-59, even in the latest build 4.2a SR1 (4.21.5.0790) [:(]

0572.Logos4Crash.txt

216483.Logos4.log

Working with other passages does not seem to be a problem. [*-)]

Can anyone reproduce a crash when trying to create a Classic format handout for this passage ?

Dave Hooton

https://community.logos.com/discussion/comment/227330#Comment_227330

Can anyone reproduce a crash when trying to create a Classic format handout for this passage ?

Mine was created as an A4 Booklet typing the passage into the Reference box. Content was:

Passage in ESV
Family Tree Adam to Abraham
Ministry of Jesus (Places)
Family Tree Jesus Mt 1:1-17

I deleted the last item and it was replaced by "The Light of the World".

But no crashes. Yours might be content related, so provide more detail.

Mark Barnes

https://community.logos.com/discussion/comment/227337#Comment_227337

David,

I think it's likely that's there's some problem with a resource on the index that relates specifically to this passage. I don't think the problem is with handouts itself.

Your logs have a number of errors, such as:

MediaMetadata Unparsed reference: popup.pos=ABBR.CENT|res=LLS:ZEB01|type=jump
RichTextReference Could not load reference: papias.3.3
TextBlockUtility TextBlockUtility.IsTextTrimmed breaks Text bindings; use TextBlockUtility.BindableText instead.

All of these are fairly common, and I don't think anything to be concerned about. However, you've also got:

BitmapSourceUtility An event was unable to invoke any of the subscribers (Exception from HRESULT: 0x80040201)

This is much rarer, and I suspect therefore the root cause. The actual error message is generated by WPF, so I'd be interested to know what the Windows Event Log makes of your crashes. Does it blame .NET, or Logos?

Also, does running a full passage guide on the passage, (clicking 'more' in each section) also cause the crash. If so, can we have a complete Logos 4 log for that? What about an Exegetical Guide?

David Wilson

https://community.logos.com/discussion/comment/227352#Comment_227352

I'd be interested to know what the Windows Event Log makes of your crashes.

Is there a specific Windows Event Log file I should be checking Mark ?
When the crash occurs, Microsoft Windows identifies that Logos Bible Software 4 stopped working.

In an attempt to reproduce this problem from scratch I deleted the previously modified handouts from My Content; then did a Sync Now to try to ensure this was not downloaded again from the server.

Using Passage Guide on John 8:31-59, I waited until the "working" bars had completed on Commentaries and Handout.

The default handout in Thin format contains three items, the passage NRSV text, the Family Tree Adam to Abraham and the Ministry of Jesus Map.

Apparently stable so far. Next click the "edit" in the handout section to bring up the Handout window. Wait again to ensure things remain stable.

Edit Author to "Wednesday Evening Life Group". Edit Organization to "Church of the Resurrection"

Change layout from "Thin" to "Classic" using lower left pull down menu. (This adds a fourth item to the handout "Family Tree : Jesus (Mt 1:1-17)

Promote the "Light of the World" illustration to the fourth spot and Family Tree Jesus slips to a newly created fifth spot.
(Handout view remains on Page 1 throughout so far.)

Change date from today's date to March 2nd (the group's meeting night) - still stable:
(Previously crash had occurred by now - possibly due to downloading the previous My Content handout version from the server ?)

Click the right arrow to flip through the pages of the handout.

Issues to note at this point: While the left "Item content" pane, shows the chain line dividing included from excluded content between two versions of "Family Tree: Jesus" and indicates there a five items in the handout content, a flip though the page view of the handout indicates that for the third item, the Ministry of Jesus map, only the heading is present at the foot of page 3, and no Map is included.

Page 1: NRSV passage text (part)
Page 2: Family Tree: Adam to Abraham, followed by remaining NRSV passage text
Page 3: "The Light of the World" picture plus full caption text, folowed by some blank space and then the Title for the "Ministry of Jesus" map, and a truncated caption reading only "Chronologically speaking, it is not possible to sequentially arrange the events in the life of" (no map - not enough space for it !!)
Page 4: Top half of page blank, bottom half contains the Family Tree: Jesus (Mt 1" 1-17)

Items Content pane to the left shows five items as part of the Classic layout content in the following sequence:

(Passage text - NRSV) John 8:31-59
Family Tree: Adam to Abraham
Ministry of Jesus (Map)
Light of the World (illiustration and lengthy caption)
Family Tree: Jesus (Mt 1:1-17)

My hunch is that when I then exit the Handout window after editing the content, this somehow creates the problem per a corrupt handout file in My Content as it is not practical to place all of these items completely into the handout (as is obvious from flipping through the views of the individual pages), despite the fact that the item content list in the left pane seems happy to think that all five items could be included. The decision on how much can be included is automatic within the software. All I did was to promote "The Light of the World" illustration and caption to item 4 in that list. The software is apparently not correctly calculating the amount of page space required to accomodate each item in the Classic Page layout.

If instead of leaving the editor here, I switch the layout back to the default "Thin" layout, the item content pane to the left flips to allowing only the top three of the items in this layout (excluding "The Light of the World" and "Family Tree: Jesus (Mt 1:1-17)".

If I then flip it back to Classic layout, it includes "The LIght of the World" as a fourth item but no longer tries to add the fifth item "Family Tree: Jesus (Mt:1 1-17)"
This time a page flip reveals the Map to be there as expected on Page 3 and the "Light of the World" illustration and caption to be moved to Page 4.

Subsequent flips between Classic and Thin layout do NOT reproduce the problem five item content.

I used my backup computer runnng WIndows Vista this time - no crashes as I have not closed the Handout edit window on a layout that apparenmtly could not work. But the original problem layout using the classic view was created on my newer Windows 7 machine. To me this suggests the problem is within Logos and the initial decision on how much content could now be accomodated in that first switch from Thin to Classic layout (when it apparently decided on a scope and sequence that would not actually fit the pages properly).

Work around seems to be to verify the individual pages after resequencing items to ensure that what you were expecting per the item content pane is what you are actually seeing on the pages ( in the past I have normally done that - must have missed it earlier this week).

Second issue with layout using the Thin layout format: If I promote "The Light of the World" illustration to the third content item to replace the Ministry of Jesus map (which on this occasion I did not need as it had been included several times already during the course of our study of John's Gospel), then the two items are exchanged and the "Light of the World illustration is included on Page 4 of the Thin layout Handout BUT the extensive caption is truncated and individual lines of the caption do not even wrap properly in the assigned space on the handout. This is inappropriate given that the top part of the assigned page is left complelety blank, so the page actually has plenty of space to include the full caption if properly laid out.

Dave Hooton

https://community.logos.com/discussion/comment/227386#Comment_227386

In trying to follow your steps (I'd not generated my original from PG) I encountered none of the issues described but then I couldn't get a fifth included item as dragging merely inserted the item and dropped the bottom item. I'll have to leave this to those more familiar with Handouts.

Mark Barnes

https://community.logos.com/discussion/comment/227386#Comment_227386

Is there a specific Windows Event Log file I should be checking Mark ?
When the crash occurs, Microsoft Windows identifies that Logos Bible Software 4 stopped working.

<edit>No need for this now. I can get my own! (see below)</edit>

The application event log for the date and time of the crash(es). You can get the date/time from the logs your uploaded if you need to. In Windows 7, if you click on the appropriate error row, you'll get the details in the general tab below. Could you copy/paste those details here, if they exist?

To find the application event log, got to the Windows Start button, type event log in the search box and click View Event Logs. Then expand the Windows LogsApplication. section and choose

Mark Barnes

https://community.logos.com/discussion/comment/227386#Comment_227386

Result! Just got the same crash. That rules out indexing/resource/.NET problems that are specific to your machine.

It could point to a faulty resource that we own that Dave doesn't, or it just may be that our libraries are bigger than his. But the fact that it's reproducible on another account/machine means there must be some underlying fault which we're not going to be able to fix here. The best you'll manage here is a workaround (which you're managing pretty well without us!).

I'll do some more investigating, and then create a bug report for you.

<edit>Bug report now here. Hopefully we'll get a response on Monday or Tuesday from Logos on it.

My initial thoughts are that it's the family trees that are causing the problem. If you can delete these from your handout, then close and re-open it to free up your memory, you'll probably be able to proceed. </edit>

David Wilson

https://community.logos.com/discussion/comment/227464#Comment_227464

Could not figure out how to get this information on my Windows Vista backup machine but can generate this for my main Windows 7 machine if still needed.

David Wilson

https://community.logos.com/discussion/comment/227469#Comment_227469

Result! Just got the same crash.

Thanks for putting the time in on this one Mark: not an easy one to reproduce for sure, but as it was causing me problems on both my main Windows 7 system and my backup Windows Vista machine, I was reluctant to attribute it to machine only.

Seems to relate to inadvertantly closing the Handout editor while having the item content pane of the Handout Editor assign more content than can fit into that specific handout layout. I was able to stop the crashes after I deleted the problem file and syncing to get it off the server and stop it downloading again. The crash occurred not due to the presence of this problem handout file alone, but when the current passage guide search was pointing to that passage and hence the problem handout file was being called up as a relevant part of "my content". Sync downloading from the server spread the problem handout to my other system and caused that to crash also when referencing the same passage (but only when referencing the same passage).

If it helps, my Library currently contains 6313 resources, so we likely have a fair number in common.

Melissa Snyder

https://community.logos.com/discussion/comment/227522#Comment_227522

Result! Just got the same crash.

Thanks for putting the time in on this one Mark: not an easy one to reproduce for sure, but as it was causing me problems on both my main Windows 7 system and my backup Windows Vista machine, I was reluctant to attribute it to machine only.

Seems to relate to inadvertantly closing the Handout editor while having the item content pane of the Handout Editor assign more content than can fit into that specific handout layout. I was able to stop the crashes after I deleted the problem file and syncing to get it off the server and stop it downloading again. The crash occurred not due to the presence of this problem handout file alone, but when the current passage guide search was pointing to that passage and hence the problem handout file was being called up as a relevant part of "my content". Sync downloading from the server spread the problem handout to my other system and caused that to crash also when referencing the same passage (but only when referencing the same passage).

If it helps, my Library currently contains 6313 resources, so we likely have a fair number in common.

I'm not able to reproduce the OOM crash going through each of your steps, with preferred Bible set to NRSV. When I select the 'Classic' theme, the 'Family Tree: Jesus (Mt 1:1-17)' remains below the dotted line and the preview is correct as I page through the handout.

It does take a few seconds for changes to take affect. I'm wondering if the handout is still in process of making a change when something else is clicked.