[resolved] CRASH: Report Typo
Logos 6.3 Beta 2 Mac OS 10.10.3
Selected a random word from Metzler's Textual Commentary and Report Typo from the right click menu. Clicked into the active window with report typo dialog still open. Logos was replaced by the Apple Crash Report
Comments
-
Tried this again 13 hours later with a different resource—IIVP Bible Background Commentary: NT. Same result.
0003.LogosLogs.jackcav.20150426-203128.zip
This crash is 100% repeatable.
0 -
bump-it
Dave
===Windows 11 & Android 13
0 -
Jack Caviness said:
This crash is 100% repeatable.
Jack can you please test this and see if it still crashes in Beta 3? I am not able to reproduce in the current version.
0 -
-
Angela Murashov said:Jack Caviness said:
This crash is 100% repeatable.
Jack can you please test this and see if it still crashes in Beta 3? I am not able to reproduce in the current version.
Oops! Forgot to test this [:$]
Mac OS 10.10.3 Logos 6.3 Beta 4
Don't know about Beta 3, but it still causes a crash in Beta 4
7357.LogosLogs.jackcav.20150506-061357.zip
Tried again with a single resource (NKJV) open: Selected random word, Start Sample log, Report Typo from right click menu for random word, click on Logos window away from report typo popup, instant crash.
Sample log—4426.LogosLogs.jackcav.20150506-061919.zip
Apple Crash Report—5383.Apple Crash Report 2.rtf
Logs after crash—7140.LogosLogs.jackcav.20150506-062039.zip
0 -
Jack Caviness said:
Oops! Forgot to test this
Mac OS 10.10.3 Logos 6.3 Beta 4
Don't know about Beta 3, but it still causes a crash in Beta 4
Thank you for providing me the steps and logs. [:)] I was successfully able to reproduce this on Mac in 6.3 Beta 4 and I will create a case to get this fixed.
0 -
Angela Murashov said:Jack Caviness said:
Oops! Forgot to test this
Mac OS 10.10.3 Logos 6.3 Beta 4
Don't know about Beta 3, but it still causes a crash in Beta 4
Thank you for providing me the steps and logs.
I was successfully able to reproduce this on Mac in 6.3 Beta 4 and I will create a case to get this fixed.This should be fixed in 6.3 Beta 5.
0 -
Angela Murashov said:
This should be fixed in 6.3 Beta 5.
Very nice—fix confirmed. Thank you for the rapid fix.
0
