Greg Terry Posted July 1, 2012 Share Posted July 1, 2012 I discovered by accident that I can make Accordance quit consistently by triple clicking on a blank area in the text window. If I have only a verse or two showing and triple click immediately below the text but not on a word, Accordance quits every time without warning. I should say I have the latest version of Accordance and am running the latest version of OSX also. Link to comment Share on other sites More sharing options...
Michael J. Bolesta Posted July 1, 2012 Share Posted July 1, 2012 I cannot replicate this. Accordance 9.6.2, Lion 10.7.4 Link to comment Share on other sites More sharing options...
Steve Carruth Posted July 1, 2012 Share Posted July 1, 2012 This is true for me as well on 9.6.2 using lion. Link to comment Share on other sites More sharing options...
Steve Carruth Posted July 1, 2012 Share Posted July 1, 2012 This is true for me as well on 9.6.2 using lion. What I mean is it crashes on me consistently when I triple click in a space after the verse. Link to comment Share on other sites More sharing options...
JonathanHuber Posted July 1, 2012 Share Posted July 1, 2012 I can replicate it, running latest versions of Accordance and OS X. Edit: this happened with the ESVS. Link to comment Share on other sites More sharing options...
Rod Decker Posted July 2, 2012 Share Posted July 2, 2012 This may be related to a problem I experienced a few weeks ago and reported here: http://www.accordancebible.com/forums/index.php?showtopic=7701 But I *cannot* replicate the triple click crash reported here. I'd guess is there is some other factor necessary to provoke this behavior. It will help the Accordance team if you can copy the crash report from the Console and paste the relevant section into this thread. You can compare the crash log that I posted in the thread linked just above to see if there is anything in common. It's sporadic bugs like this that drive programmers crazy, so the more detail on the crash multiple users can offer the more help it will be to those tasked with trying to figure out what the "magic" combination is that causes it. Link to comment Share on other sites More sharing options...
Greg Terry Posted July 2, 2012 Author Share Posted July 2, 2012 It never fails to crash when triple clicking in a blank area below the text. Here is the report from Console.app for the crash: 7/1/12 11:03:30.884 PM [0x0-0x20020].com.OakTree.Accordance: An unhandled exception occurred at $001782A4 : 7/1/12 11:03:30.884 PM [0x0-0x20020].com.OakTree.Accordance: EAccessViolation : Access violation 7/1/12 11:03:30.884 PM [0x0-0x20020].com.OakTree.Accordance: $001782A4 7/1/12 11:03:30.884 PM [0x0-0x20020].com.OakTree.Accordance: $00177FE4 7/1/12 11:03:30.884 PM [0x0-0x20020].com.OakTree.Accordance: $00177D41 7/1/12 11:03:30.884 PM [0x0-0x20020].com.OakTree.Accordance: $00253ADD 7/1/12 11:03:30.884 PM [0x0-0x20020].com.OakTree.Accordance: $002BAD60 7/1/12 11:03:30.884 PM [0x0-0x20020].com.OakTree.Accordance: $000BB778 7/1/12 11:03:30.884 PM [0x0-0x20020].com.OakTree.Accordance: $000AC4C6 7/1/12 11:03:30.884 PM [0x0-0x20020].com.OakTree.Accordance: $003640B3 7/1/12 11:03:30.884 PM [0x0-0x20020].com.OakTree.Accordance: $00397B0C 7/1/12 11:03:30.884 PM [0x0-0x20020].com.OakTree.Accordance: $00016DA1 7/1/12 11:03:30.884 PM [0x0-0x20020].com.OakTree.Accordance: $0037478D 7/1/12 11:03:30.884 PM [0x0-0x20020].com.OakTree.Accordance: $00375190 7/1/12 11:03:30.884 PM [0x0-0x20020].com.OakTree.Accordance: $9A351DEC 7/1/12 11:03:30.884 PM [0x0-0x20020].com.OakTree.Accordance: $9A1CD4F3 7/1/12 11:03:30.884 PM [0x0-0x20020].com.OakTree.Accordance: $9A 7/1/12 11:03:30.887 PM [0x0-0x20020].com.OakTree.Accordance: 1CC970 7/1/12 11:03:30.887 PM [0x0-0x20020].com.OakTree.Accordance: $9A1E1755 7/1/12 11:03:30.887 PM [0x0-0x20020].com.OakTree.Accordance: $9A35E012 7/1/12 11:03:30.895 PM com.apple.launchd.peruser.501: ([0x0-0x20020].com.OakTree.Accordance[269]) Exited with code: 217 Link to comment Share on other sites More sharing options...
Greg Terry Posted July 2, 2012 Author Share Posted July 2, 2012 A further update on this issue. It appears to crash ONLY when a tagged text is being displayed while performing the triple click on a blank spot. It will not crash with a non-tagged text or at least it didn't on the handful or so I tried. In that instance I receive the dialog box stating I need to select a word first. However, every tagged text I tried (I think that was 8 different ones) including the GNT-TR Strongs tagged text (the only only tagged non-English text I have ) crashed it instantly. That may explain why it works OK for some users and not for others. Hope that helps. Link to comment Share on other sites More sharing options...
Ken Simpson Posted July 2, 2012 Share Posted July 2, 2012 I confirm I get the crash on tagged texts...seems fine on my Gk and Hb texts (GNT-TR, NAS27-T, GNT-T, GNT-TIS, GNT-TRS, GNT-WH all ok). Crash repeatable on ESVS, NAS95S, KJVS. Link to comment Share on other sites More sharing options...
Michael J. Bolesta Posted July 2, 2012 Share Posted July 2, 2012 I confirm I get the crash on tagged texts...seems fine on my Gk and Hb texts (GNT-TR, NAS27-T, GNT-T, GNT-TIS, GNT-TRS, GNT-WH all ok). Crash repeatable on ESVS, NAS95S, KJVS. I think you found an important factor. Earlier I did not try it with an English tagged text. No crash with GNT-T, NET, NABRE. When I did so with NRSVS, Accordance crashed. Michael Link to comment Share on other sites More sharing options...
Helen Brown Posted July 2, 2012 Share Posted July 2, 2012 Thank you all. We are looking into this right now. Link to comment Share on other sites More sharing options...
R Gustason Posted July 3, 2012 Share Posted July 3, 2012 Here is my Console reports in case they are helpful: 7/2/12 11:34:11.019 PM [0x0-0x2dd2dd].com.OakTree.Accordance: An unhandled exception occurred at $001782A4 : 7/2/12 11:34:11.019 PM [0x0-0x2dd2dd].com.OakTree.Accordance: EAccessViolation : Access violation 7/2/12 11:34:11.019 PM [0x0-0x2dd2dd].com.OakTree.Accordance: $001782A4 7/2/12 11:34:11.019 PM [0x0-0x2dd2dd].com.OakTree.Accordance: $00177FE4 7/2/12 11:34:11.019 PM [0x0-0x2dd2dd].com.OakTree.Accordance: $00177D41 7/2/12 11:34:11.019 PM [0x0-0x2dd2dd].com.OakTree.Accordance: $00253ADD 7/2/12 11:34:11.019 PM [0x0-0x2dd2dd].com.OakTree.Accordance: $002BAD60 7/2/12 11:34:11.019 PM [0x0-0x2dd2dd].com.OakTree.Accordance: $000BB778 7/2/12 11:34:11.019 PM [0x0-0x2dd2dd].com.OakTree.Accordance: $000AC4C6 7/2/12 11:34:11.019 PM [0x0-0x2dd2dd].com.OakTree.Accordance: $003640B3 7/2/12 11:34:11.019 PM [0x0-0x2dd2dd].com.OakTree.Accordance: $00397B0C 7/2/12 11:34:11.019 PM [0x0-0x2dd2dd].com.OakTree.Accordance: $00016DA1 7/2/12 11:34:11.019 PM [0x0-0x2dd2dd].com.OakTree.Accordance: $0037478D 7/2/12 11:34:11.019 PM [0x0-0x2dd2dd].com.OakTree.Accordance: $00375190 7/2/12 11:34:11.019 PM [0x0-0x2dd2dd].com.OakTree.Accordance: $9BE63DEC 7/2/12 11:34:11.019 PM [0x0-0x2dd2dd].com.OakTree.Accordance: $9BCDF4F3 7/2/12 11:34:11.019 PM [0x0-0x2dd2dd].com.OakTree.Accordance: $9B 7/2/12 11:34:11.055 PM [0x0-0x2dd2dd].com.OakTree.Accordance: CDE970 7/2/12 11:34:11.055 PM [0x0-0x2dd2dd].com.OakTree.Accordance: $9BCF3755 7/2/12 11:34:11.055 PM [0x0-0x2dd2dd].com.OakTree.Accordance: $9BE70012 7/2/12 11:34:11.064 PM com.apple.launchd.peruser.501: ([0x0-0x2dd2dd].com.OakTree.Accordance[8225]) Exited with code: 217 7/2/12 11:34:40.713 PM [0x0-0x2de2de].com.OakTree.Accordance: An unhandled exception occurred at $001782A4 : 7/2/12 11:34:40.713 PM [0x0-0x2de2de].com.OakTree.Accordance: EAccessViolation : Access violation 7/2/12 11:34:40.713 PM [0x0-0x2de2de].com.OakTree.Accordance: $001782A4 7/2/12 11:34:40.713 PM [0x0-0x2de2de].com.OakTree.Accordance: $00177FE4 7/2/12 11:34:40.713 PM [0x0-0x2de2de].com.OakTree.Accordance: $00177D41 7/2/12 11:34:40.713 PM [0x0-0x2de2de].com.OakTree.Accordance: $00253ADD 7/2/12 11:34:40.713 PM [0x0-0x2de2de].com.OakTree.Accordance: $002BAD60 7/2/12 11:34:40.713 PM [0x0-0x2de2de].com.OakTree.Accordance: $000BB778 7/2/12 11:34:40.713 PM [0x0-0x2de2de].com.OakTree.Accordance: $000AC4C6 7/2/12 11:34:40.713 PM [0x0-0x2de2de].com.OakTree.Accordance: $003640B3 7/2/12 11:34:40.713 PM [0x0-0x2de2de].com.OakTree.Accordance: $00397B0C 7/2/12 11:34:40.713 PM [0x0-0x2de2de].com.OakTree.Accordance: $00016DA1 7/2/12 11:34:40.713 PM [0x0-0x2de2de].com.OakTree.Accordance: $0037478D 7/2/12 11:34:40.713 PM [0x0-0x2de2de].com.OakTree.Accordance: $00375190 7/2/12 11:34:40.713 PM [0x0-0x2de2de].com.OakTree.Accordance: $9BE63DEC 7/2/12 11:34:40.713 PM [0x0-0x2de2de].com.OakTree.Accordance: $9BCDF4F3 7/2/12 11:34:40.713 PM [0x0-0x2de2de].com.OakTree.Accordance: $9B 7/2/12 11:34:40.713 PM [0x0-0x2de2de].com.OakTree.Accordance: CDE970 7/2/12 11:34:40.713 PM [0x0-0x2de2de].com.OakTree.Accordance: $9BCF3755 7/2/12 11:34:40.713 PM [0x0-0x2de2de].com.OakTree.Accordance: $9BE70012 7/2/12 11:34:40.723 PM com.apple.launchd.peruser.501: ([0x0-0x2de2de].com.OakTree.Accordance[8232]) Exited with code: 217 7/2/12 11:35:07.542 PM [0x0-0x2df2df].com.OakTree.Accordance: An unhandled exception occurred at $001782A4 : 7/2/12 11:35:07.542 PM [0x0-0x2df2df].com.OakTree.Accordance: EAccessViolation : Access violation 7/2/12 11:35:07.542 PM [0x0-0x2df2df].com.OakTree.Accordance: $001782A4 7/2/12 11:35:07.542 PM [0x0-0x2df2df].com.OakTree.Accordance: $00177FE4 7/2/12 11:35:07.542 PM [0x0-0x2df2df].com.OakTree.Accordance: $00177D41 7/2/12 11:35:07.542 PM [0x0-0x2df2df].com.OakTree.Accordance: $00253ADD 7/2/12 11:35:07.542 PM [0x0-0x2df2df].com.OakTree.Accordance: $002BAD60 7/2/12 11:35:07.542 PM [0x0-0x2df2df].com.OakTree.Accordance: $000BB778 7/2/12 11:35:07.542 PM [0x0-0x2df2df].com.OakTree.Accordance: $000AC4C6 7/2/12 11:35:07.542 PM [0x0-0x2df2df].com.OakTree.Accordance: $003640B3 7/2/12 11:35:07.542 PM [0x0-0x2df2df].com.OakTree.Accordance: $00397B0C 7/2/12 11:35:07.542 PM [0x0-0x2df2df].com.OakTree.Accordance: $00016DA1 7/2/12 11:35:07.542 PM [0x0-0x2df2df].com.OakTree.Accordance: $0037478D 7/2/12 11:35:07.542 PM [0x0-0x2df2df].com.OakTree.Accordance: $00375190 7/2/12 11:35:07.542 PM [0x0-0x2df2df].com.OakTree.Accordance: $9BE63DEC 7/2/12 11:35:07.542 PM [0x0-0x2df2df].com.OakTree.Accordance: $9BCDF4F3 7/2/12 11:35:07.542 PM [0x0-0x2df2df].com.OakTree.Accordance: $9BCDE970 7/2/12 11:35:07.542 PM [0x0-0x2df2df].com.OakTree.Accordance: $9BCF3755 7/2/12 11:35:07.542 PM [0x0-0x2df2df].com.OakTree.Accordance: $9BE70012 7/2/12 11:35:07.544 PM com.apple.launchd.peruser.501: ([0x0-0x2df2df].com.OakTree.Accordance[8236]) Exited with code: 217 Link to comment Share on other sites More sharing options...
Helen Brown Posted July 3, 2012 Share Posted July 3, 2012 We have released 9.6.3 and believe that this bug is now fixed, please confirm. Link to comment Share on other sites More sharing options...
Ken Simpson Posted July 3, 2012 Share Posted July 3, 2012 For me, triple clicking in the blank space after a verse in a tagged English text does not trigger a silent quit anymore. However, if I triple click in other text modules i get the warning "In order to search for words, there must be a valid selection in the pane." This does not occur when I triple click in an English tagged text, so the behaviour is still a little different. While this is obviously not a critical difference, I presume it is significant. Thanks for keeping on squashing those pesky bugs guys! Link to comment Share on other sites More sharing options...
Greg Terry Posted July 3, 2012 Author Share Posted July 3, 2012 No crash for me after update! I agree with everything Ken says - especially . . . . Thanks for fixing the bug so quickly! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.