Crash: L5 involving sense database

I've been crashing L5 periodically for the last 2 or so weeks. It's very predictable, so I've been careful not to do it: clicking on a RI 'sense' row. The routine will open a new window, populate the left side up to the point where it's looking for choices. And then crash.

Similarly on my BWS, when it gets to the sense section it's a guarenteed lockup/crash.

I'm hoping to simply wait for an update. However the last update didn't do anything, so I assume it's in one of the databases.

.4743.LogosErrorFiles.zip.

Find more posts tagged with

Comments

MJ. Smith

I've been trying to get Logos' attention on a similar problem. http://community.logos.com/forums/t/62851.aspx It is keeping me from finishing the BSL wiki page.

Thomas Jackson

DMB,

My L5 will crash every time I run the Bible Sense Lexicon. Tech support is working on the problem (2 days and counting). Do not know if this is related to your problem, however, I will post an update when tech support comes up with a fix.

Thomas

DMB

https://community.logos.com/discussion/comment/445228#Comment_445228

Thank you MJ and Thomas.

Following my predictable BWS sense-section crash, I decided it would be most intelligent to remove the sense section from my template. That's when I noticed that editing the BWS template is a disaster in and of itself ... whole sections were duplicated throughout. I can't quite figure out what causes that; no amount of deleting repeated sections would prevent even MORE sections to appear. Eventually I had maybe 30 or more duplicated sections. Well that's another issue.

The only solution was to always edit the BWS template with a clean layout and nothing else showing.

Thomas Ball

DMB:

I'm sorry for the trouble regarding the sense section in RI. (I'm assuming RI means Reverse interlinear? If not please clarify. Screenshots of what you mean would be helpful.) Where in the reverse interlinear on the "sense" section are you clicking? A specific word or anywhere in the row? What book are you using and where in the book?

MJ: I'm sorry you haven't gotten a reply. I think QA's manpower has been depleted since middle-end of last week. I'm not sure when everyone will be back, but I would assume after the new year at the latest. I can't reproduce the behavior your describe in the other thread on the stable build, so if it is consistent with others' experiences then it is isolated to the beta.