Layout Crash (5.0b Beta 1 5.0.2.0441) with logs

Luke Burgess

 

 

Bug: 

Switching between saved layouts causes program to crash

Description
If I start normally (without a blank layout), and select a saved layout, the program crashes. If I start with a blank layout and then switch to a saved layout it works the first time, but if I  choose a different layout the program will crash

Steps to reproduce

1. Start the program with any non-blank layout
2. Select a saved layout, the program crashes with the dialog box that instructs the user to close the program

 

 

 

1. Start the program with a blank layout
2. Select a saved layout
3. Select a second saved layout, the program crashes

 

 

Actual Result
Crash
Expected Result
I expect the layout to be displayed

System Specs
Desktop | Windows Experience Index: 5.9 | AMD Athlon II X4 640 | 8GB RAM | Dual 22” widescreen monitors at 1920x1200 | Windows 7 Home Premium

Comments
Please Help

LOGS: 1425.logoslogs.zip

 

Rich DeRuiter

Switching between saved layouts causes program to crash

I've not had this problem.

Looking at your logs, I notice that your Logos.log has a date stamp (10:54AM) after your error log (10:46AM), and ends without closing or crashing. I suspect you ran logos after the crash and before uploading. Next time, it would be helpful to upload the Logos.log after the crash and before restarting Logos.

There is nothing in the logs that looks particularly helpful, since we can't tell which resource or layout is causing the problem.

It's possible that there is a problem with your NLT reverse interlinear, or its index, as several warnings appear concerning milestones, the last of which references RVI:NLTNT. But I really don't know if this is the cause of your crashes or not. If that resource is used in those layouts that are crashing, there may be a chance that it is the cause. Normally, these warnings don't report info that may result in a crash, but you never know. If you have the time, you could try to fix the RVI:NLTNT issue by carefully following these instructions:

• Hide the NLT
• Restart Logos and let it finish indexing.
• Ensure that the NLT does not appear in your library nor in your Logos resource folder (C:\Users\Luke\AppData\Local\Logos4\Data\iyqh2gis.4ke\ResourceManager\Resources - look for NLT.logos4 and NLTNT.lbsrvi - if they are still there, close Logos and delete the resources manually, then restart Logos and let it finish indexing).
• Unhide (restore) the resource (see the above article on hiding resources for instructions on restoring)
• Restart Logos and let the resource download and finish indexing.
• Try again your layouts again.

Note that if the problem is only with the resource (not with a corrupt index) update resources may fix it, but that command takes a long time to run, and it won't fix an issue that resides only in the index.

Also note that I really don't know if this will fix your layout issue. It's possible that a layout is corrupt, or something else (possibly another corrupt index/database?) is preventing this from working properly.

In either case, if this happens again, be sure to upload the Logos.log after the crash and before restarting Logos. This may give us a bigger hint about what's going on here.