L5 crash related to one resource location + highlighting
Logos 5 crashes (shut down by Windows) when I navigate to Enoch 100.3 in the Pseudepigrapha, but only if I have the Highlighting pane open.
After it crashed several times, I deleted everything in my LibraryIndex folder and waited for it to reindex. I then used the command box in L5 to open the POT to Enoch 1, closed all other resources and panes, turned off all visual filters, and was able to navigate to Enoch 100.3 okay. Then I was able to enable the visual filters, open the other resources, and open the Information and Copy Bible panes. But as soon as I opened the Highlighting pane (Tools | Highlighting), crash!
So, the crash is limited to this resource (POT) open to this place (Enoch 100), with the highlighting pane open. How on earth do I address that issue?
The attached zip file contains the Logos Log Files dated today.
Details:
- Logos: 5.2 SR-1 (5.2.0.0052)
- Resource: LLS:33.0.2; 2013-01-25T15:31:01Z; CHASPOT.logos4 = R H Charles, Pseudepigrapha of the Old Testament. Bellingham, WA: Logos Bible Software, 2004.
- Crash report: Problem Signature 09 is "System.ArgumentOutOfRange".
- OS: Windows 8.1 64-bit (6.3.9600.0.0.0.768.101).
Comments
-
I'm not able to reproduce this crash yet.
The error log appears to indicate that the problem actually originates in CBV, not in the Highlighting panel. Do you have any custom Copy Bible Verses styles? If so, how are they defined? It's possible that the crash comes from trying to output Enoch 100.3 with a custom style.
0 -
Bradley Grainger (Logos) said:
I'm not able to reproduce this crash yet.
The error log appears to indicate that the problem actually originates in CBV, not in the Highlighting panel. Do you have any custom Copy Bible Verses styles? If so, how are they defined? It's possible that the crash comes from trying to output Enoch 100.3 with a custom style.
Bradley, thank you for this.
You are right: it is the Copy Bible Verses pane and not the Highlight pane that triggers the crash.
Not sure if it's a custom style though. I've just experienced the crash using what I think is an inbuilt setting:
Fully Formatted from ESV to Microsoft Word.In any case, I'm not stuck: I can work around this issue by closing the Copy Bible Verses pane before opening the Pseudepigrapha to this location. It would be good if we can pin down and fix the issue, but it's not a show-stopper for me.
Once again, thanks for your help.
0 -
This should be fixed in 5.2 SR-3.
0 -
0
-
Angela Murashov said:
This should be fixed in 5.2 SR-3.
And it has been.
After applying 5.2 SR3, the problem no longer occurs.
That's very quick, and very much appreciated. Thanks guys.
0
