Logos Crash on Exit
Hi,
I thought these logs might be helpful because Logos again crashed while exiting. This time I first used the close all command to close all resources and then quit. Additionally I was at home and on a regular adsl connection with with no proxy rather than at college.
Hopefully these logs are useful?
Cheers,
John
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
Comments
-
Dave
===Windows 11 & Android 13
0 -
John Goodman said:
Hi,
I thought these logs might be helpful because Logos again crashed while exiting. This time I first used the close all command to close all resources and then quit. Additionally I was at home and on a regular adsl connection with with no proxy rather than at college.
Hopefully these logs are useful?
Cheers,
John
John,
Thanks to your persistence (and all the other Mac users who report bugs and post logs), I think we have a fix for this crash on quit. It seems there was a bug in Mono that we were finally able to track down earlier this week.
It seems this bug was a race condition that could occur when Logos was running when waking from sleep. There was about a 10 second window when waking from sleep in which Mono could think that some internal book-keeping data was no longer necessary and throw it out. When this occurred, the program might crash while running, but more often than not it resulted in a crash on quit.
This might also explain why people who quit Logos Mac before putting their Mac to sleep had a more stable experience, as this bug appears to only occur when waking from sleep.
We have a fix that should resolve the issue in the first 5.2a beta. We'll monitor the crash reports for the 5.2a beta when it ships and see if the number of reports for this issue decreases in 5.2a. If we determine that the change is effective, we'll push this change back to the stable releases as well.
Mobile Development Team Lead
0 -
Tom,
I'm excited to see if it works out?!
Cheers,
John
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
This has been a problem for me for as long as I can remember. In fact, I don't think I've been able to close Logos without a Force Quit except for a couple of times. Every time I've mentioned it to tech support at Logos all I receive in response is, "That's strange. It shouldn't do that." (Yeah, thanks.)
Hopefully this will indeed fix it.
0 -
I'm glad to see I'm not the only one. I'm a new Logos user (2 months or so) and on my MacBook Air (2011 Core i5 with plenty of RAM and a FRESH install of OSX Mavericks) Logos always crashes on Command+Q, and usually when I do a "File+Quit". For software that cost me hundreds and hundreds of dollars this is a little frustrating. There's a new update almost every time I open it, indexing after each update (what does that mean anyway) and then the closing issue. I switched from Windows to Mac 6 years ago because of nonsense like this. I know Logos is the gold standard in content, but I'm starting to have buyer's remorse and thinking Accordance might have been the better choice for me.
0 -
Jeff, while I understand your frustration, I own copies of both Accordance and logos. They are both great software but their approach to implementing Bible study is different.
While I do enjoy using Accordance and it has some powerful features, it lacks features like the Guides and the Clause search, a well integrated notes system and a rocking iPad app. The personal books in Logos are easier to use as well.
I highly recommend to check out the learn logos.com website and some of their trainings and you will discover how powerful Logos can be.
Hope that helps. I do have a in depth comparison of both software on my blog if you are interested. therenewedmind.org. In my opinion, Logos is rat the moment the most powerful, versatile, flexible and advance Bible study software in the market. To me that offset any issues I may have with it until they get fixed and improved.
David
0 -
Tom,
I'm curious to know if this bug is squished in 5.2 SR 4?
Cheers,
John
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
John Goodman said:
I'm curious to know if this bug is squished in 5.2 SR 4?
As per Tom's response above, the fix is in 5.2a, currently in beta.
0 -
So what does the 'a' refer to? Which stable release would have it? 5.3?
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
John Goodman said:
So what does the 'a' refer to?
The "a" stands for ahhh... nothing. That is just the release "number."
The current release is "Logos 5.2 SR-4" ("SR" stands for "service release). The next stable release version will be called "Logos 5.2a" (currently in "beta 2"). Typically, you don't add another "point" number to the end except when there are significant new features.
As was said previously, the fix should be released to stable channel when 5.2a goes live.
0 -
More info (in case you are interested):
Logos 5 has had 7 "major" releases. You can find the "release notes" in the wiki HERE. For each of these releases, you will see various "SR's" & "RC's." An "RC" (Release Candidate) is a beta version which is considered "stable." If you were to ever venture into beta testing, doing so during the RC stage would be advised... but only do so with all the regular warnings.
- 5.0
- 5.0a
- 5.0b
- 5.1
- 5.1a
- 5.1b
- 5.2
0 -
thanks that makes sense.
I'm just excited because when it does come out I'll be able to demo Logos to someone without it starting with a crash!
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
John Goodman said:
I'm curious to know if this bug is squished in 5.2 SR 4?
No, not yet. We have discussed pulling the fix back into 4.6 and 5.2, but we wanted to get at least one more 5.2a beta release under our belts to see if the fix caused any other problems. So far the results look promising.
Mobile Development Team Lead
0 -
Tom Philpot (Logos) said:
No, not yet. We have discussed pulling the fix back into 4.6 and 5.2, but we wanted to get at least one more 5.2a beta release under our belts to see if the fix caused any other problems. So far the results look promising.
The fix for this crash will be in 5.2 SR-5.
0 -
I can confirm that the issue is fixed... awesome!
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0
