Close multiple panels from main window with close button.
Logs attached.
34048.Logos4Crash.txt
3730.Logos4Error.log
1072.awesomium.log
May the Grace & Peace of our Lord Jesus Christ be with you!Pastor Bill, Faith Presbyterian Church
W8 64bit, Office 2010 i7, 2.40GHz, 1Gb graphics, 8Gb RAM, 7200rpm 750Gb hybrid diskHTC Incredible 2, Droid 2.3.4
BillS: Close multiple panels from main window with close button. Logs attached. 34048.Logos4Crash.txt 3730.Logos4Error.log 1072.awesomium.log
Bill, did you also save the Logos4.log file before restarting Logos? If so, could you post that here too?
It's hard to tell with the logs here, but it looks like a problem saving the active layout. I'm not sure what would cause that, though there are a number of possibilities. According to the Logos4Error.log It looks like the same issue you had 3X on April 7 (last Saturday), but not the same you had on April 9 (Monday).
Are you experiencing any other issues with Logos4? Does it typically startup and shut down normally?
Help links: WIKI; Videos; Logos 5 FAQ (Phil. 2:14, NIV)
Frequent crashes on close, no other issues (that I know of)... this was the 1st on b6, but it had been crashing on close FREQUENTLY (but not always) on b5.(EDIT: that behavior--frequent but not always--appears to be continuing into b6. I just tried closing it with the close button, & close worked fine. I expect I'll have another crash again soon, though.)
Though I've started Logos since then (am working on sermon, today), the Logos4.log file is dated even earlier--the day before (4/11), so I'll attach it.
7674.Logos4.log
BillS:Though I've started Logos since then (am working on sermon, today), the Logos4.log file is dated even earlier--the day before (4/11), so I'll attach it.
Yes, that's an old log. If you don't have logging enabled, why don't you do that and load the Logos4 log here next time you get a crash.
OK, logging enabled... will post next time it crashes....
BillS:Close multiple panels from main window with close button.
This is very similar to the crash I've experienced since Beta 2 - http://community.logos.com/forums/t/46439.aspx
Dave===
Windows PC, Android phone
Dave Hooton: BillS:Close multiple panels from main window with close button. This is very similar to the crash I've experienced since Beta 2 - http://community.logos.com/forums/t/46439.aspx
Thanks, Dave.... logging is enabled. I'll post logs when it happens again. And it will....
Started opening & closing it... Moments ago, it crashed. Interestingly, it attempted sync after closing & it was while sync was being attempted that the crash happened. However, these are the only logs dated today.
5635.Logos4.log
3582.Logos4Crash.txt
2021.Logos4Error.log
BillS:Started opening & closing it... Moments ago, it crashed. Interestingly, it attempted sync after closing & it was while sync was being attempted that the crash happened. However, these are the only logs dated today.
It looks like it's crashing while trying to save the active layout, as mentioned above. I have no idea why it would do that.
When you close, do you ensure that the sync arrows are finished 'circling the drain' before closing? This would explain the sync after closing routine (which appears to have completed successfully in the Logos4.log (if I'm reading it right).
Richard DeRuiter:When you close, do you ensure that the sync arrows are finished 'circling the drain' before closing?
No, as I was deliberately trying to provoke a crash... I do everything I can to provoke bad behavior in the app. If it actually behaves badly & crashes, then I feel I've helped in finding a bug. Isn't that the purpose of beta?
More seriously, I didn't pay any attention but you're probably right. Even if that's the case, I'd still expect L4 to stop gracefully, not crash.
BillS:No, as I was deliberately trying to provoke a crash..
I wasn't trying to provoke it when it crashed in B6!
Dave Hooton: BillS:No, as I was deliberately trying to provoke a crash.. I wasn't trying to provoke it when it crashed in B6!
Nor am I, usually, Dave. I just figured it'd crash sooner or later if I opened/closed it enough times. And this one was typical of one of three characteristic failures on close . The other one doesn't seem to involve Sync. It just crashes. The 3rd? Sometimes, if it crashes on close it crashes again on the next open.... but will open fine on the open after that.
Why is this "provoked" crash an issue fo rme? Often, I need to shut down in a hurry because I need to leave (home for the office or vice versa).The laptop needs to go with me, as it's my only PC. I may not check whether sync has completed or not. I'm too focused on getting where I'm supposed to be. IMO, the software needs to be prepared for a hurried shutdown. (I won't be the only one who has this issue.)
This should be fixed in the next beta.
Bradley Grainger (Logos): This should be fixed in the next beta.
Thanks, Bradley!