CRASH: Unticking Propositional Outlines

3782.Logos Log Files.zip

I'll take a look at this issue. Thanks!

I haven't been able to reproduce the issue. It's possible that this issue has been fixed in a build that will be shipping soon. However, I need your main log file (Logos.log) to be able to diagnose the issue further.

Please follow the instructions here to enable logging (which allows you to get the Logos.log file from your log files folder): https://www.logos.com/support/logos6/mac/report-problem

Thank you!

Thanks Chris ... if the issue reoccurs I'll know it's still live and will enable logging and repost log. I can't follow the instructions in the link as I'm on Windows but I can find the equivalent.

Oh sorry about that! Here's the Windows link just in case: https://www.logos.com/support/logos6/windows/report-problem

No problem. The issue just reoccurred. Here's the Logos.log just created.

4807.Logos.zip

Thanks for the additional information! I will take another look at this.

I still have not been able to reproduce the issue after trying for several hours. Can you post the support info for NIV that you are encountering the crash with (click the "i" button near the top right and scroll down to the bottom)? It should look something like this:

LLS:1.0.10

2014-10-30T03:55:23Z

NIV.logos4

RVI:NIVNT

2014-10-30T03:42:58Z

NIVNT.lbsrvi

Can you reproduce the issue when you start from a completely blank layout and only open the NIV1984 and then enable propositional outlines? Thank you.

Yes I can reproduce from a blank layout. All I have to do is open any Bible with Propositional Outlines, and navigate to an NT passage with that option ticked.

LLS:1.0.10
2014-10-30T03:55:23Z
NIV.logos4
RVI:NIVNT
2014-10-30T03:42:58Z
NIVNT.lbsrvi

Bummer. I can't reproduce it now either!!

Hmmm, ok. Thanks for trying! Please let me know if you encounter the issue again. If you do end up encountering it again and you are able to, please post the support info for the resource (if it's a different resource than what you just posted) and the location in the resource (e.g. John 1:1).

Thank you. 

Sure will do. It happened with other passages too e.g. 1 Peter.

Just happened again. It seems OK after "Do not show in any resources" is selected, but as soon as "Show In All Resources" is switched on, it starts happening.

Is it possible the issue is with a different resource than the NIV (1984)? When you enable "Show In All Resources" for propositional outlines, does it crash immediately if you only have the NIV (1984) open? Or do you open another resource later that causes the crash (if so, which resource)? Also, are there other resources open when you enable "Show In All Resources" besides the NIV (1984) and if so, which resources?

If you can give me as much information as possible, it will help me greatly in reproducing and fixing the issue. Thank you.

Haven't been able to reproduce it since last post despite trying all the combinations I could think of regarding Bible versions, passages, Prop. outlines options etc. Just installing latest update now so will see if it happens again.

Cheers
Richard

Is it possible to send you a layout? I can reproduce it as follows:

1. Open blank layout
2. Open ESV and select "Show in all resources" for Propositional outline
3. Open a certain saved layout from my list and the crash happens.

Cheers
Richard

Yes, I will contact you by email directly with instructions. Thanks for helping me track this down!

This is caused by enabling propositional outlines in certain resources with interlinear content (in this case, the version of the NA27 with resource id LLS:1.0.317). A fix has been made internally and we will update this thread when it ships in a build. Thank you!

This is caused by enabling propositional outlines in certain resources with interlinear content (in this case, the version of the NA27 with resource id LLS:1.0.317). A fix has been made internally and we will update this thread when it ships in a build. Thank you!

This fix just shipped in 6.0b Beta 2.

According to the release notes, this should also be fixed in 6.0a SR-5 that just shipped.