Every time I launch Logos after it was closed following a session, when it was using a multi-panel layout, I get a message telling me that Logos crashed last time it was closed and inviting me to send a crash report to Logos. I always agree, after all it may contain something which can help the programmers. (Occasionally I type a little message in the note box saying that it didn't really crash. Most times I just post the report.)Believe that is a known bug. Can't find it now, but one of the dev team responded to a previous post about this situation. Believe it is fixed in 5.2a beta, as I no longer experience it.
The Crash That Isn't
Alan Macgregor
Member Posts: 2,438 ✭✭✭
Every time I launch Logos after it was closed following a session, when it was using a multi-panel layout, I get a message telling me that Logos crashed last time it was closed and inviting me to send a crash report to Logos. I always agree, after all it may contain something which can help the programmers. (Occasionally I type a little message in the note box saying that it didn't really crash. Most times I just post the report.)
Am I the only one who experiences this, or is it a common occurrence?
Every blessing
Alan
PS Is anything being done by Logos about this anomaly?
iMac Retina 5K, 27": 3.6GHz 8-Core Intel Core i9; 16GB RAM;MacOS 10.15.5; 1TB SSD; Logos 8
MacBook Air 13.3": 1.8GHz; 4GB RAM; MacOS 10.13.6; 256GB SSD; Logos 8
iPad Pro 32GB WiFi iOS 13.5.1
iPhone 8+ 64GB iOS 13.5.1
0
Comments
-
Alan Macgregor said:
Am I the only one who experiences this, or is it a common occurrence?
I've never had this experience. Sounds like a bug to me.
Using adventure and community to challenge young people to continually say "yes" to God
0 -
Alan Macgregor said:
Every time I launch Logos after it was closed following a session, when it was using a multi-panel layout, I get a message telling me that Logos crashed last time it was closed and inviting me to send a crash report to Logos. I always agree, after all it may contain something which can help the programmers. (Occasionally I type a little message in the note box saying that it didn't really crash. Most times I just post the report.)
Believe that is a known bug. Can't find it now, but one of the dev team responded to a previous post about this situation. Believe it is fixed in 5.2a beta, as I no longer experience it.
0 -
See Tom Philpot's reply here: http://community.logos.com/forums/p/81201/574827.aspx#574827
Every blessing
Alan
iMac Retina 5K, 27": 3.6GHz 8-Core Intel Core i9; 16GB RAM;MacOS 10.15.5; 1TB SSD; Logos 8
MacBook Air 13.3": 1.8GHz; 4GB RAM; MacOS 10.13.6; 256GB SSD; Logos 8
iPad Pro 32GB WiFi iOS 13.5.1
iPhone 8+ 64GB iOS 13.5.1
0 -
Alan, I think this should be fixed now.
Thanks,
Tom
Mobile Development Team Lead
0 -
It was fixed in SR2 [:D] … but it is back again in SR3. [:'(]
iMac Retina 5K, 27": 3.6GHz 8-Core Intel Core i9; 16GB RAM;MacOS 10.15.5; 1TB SSD; Logos 8
MacBook Air 13.3": 1.8GHz; 4GB RAM; MacOS 10.13.6; 256GB SSD; Logos 8
iPad Pro 32GB WiFi iOS 13.5.1
iPhone 8+ 64GB iOS 13.5.1
0 -
Alan Macgregor said:
It was fixed in SR2
… but it is back again in SR3. 
It looks like Tom is looking into this: http://community.logos.com/forums/t/83533.aspx.
0
