Jump to content

Ugh - crashes not fixed in the 14.0.6.0


Cnthetford

Recommended Posts

Accordance has been plagued by frequent freezes and crashes since the introduction of version 14.  If I type in verse references to navigate to passages, sooner or later it is going to crash or freeze, meaning I have to re-start every 10-15 minutes.  I was excited to see the latest update, hoping that these problems would be fixed.  They are so pervasive, it seems like they would be a priority.  However, the problem is still there.  Things were working well for a while, but about 15 minutes into looking at different passages, I entered "1Jn 2:15-17" and the program crashed again.

 

Accordance Crash Log
Crashed at: 6:4:49:61 On: 2 of Jul, 2023  Central Daylight Time

Accordance 14.0.6 (14.0.6.0)
Windows 10 (10.0.22621)
RAM: 5928MB free of 16309MB total
Disc: 430GB free of 931GB total


Range check error
Address:   $0044E041

Backtrace: 
  $0044E041
  $00859D0A
  $009127ED
  $00912611
  $00914E49
  $004E177B
  $00915318
  $004E18E0
  $009057CC
  $007B4E95
  $007B4BAC
  $007B4806
  $007B2B0B
  $004E3570
  $004FB92A
  $004EBB2F
  $0095EDFE

Link to comment
Share on other sites

Thanks for this. I'll get this reported.

Link to comment
Share on other sites

What Bible were you in when it crashed?

Link to comment
Share on other sites

Probably ESVS.  That is the one I typically use.

Link to comment
Share on other sites

I'll try this on my Windows PC next time I'm at it. I'm on Windows 11, so I'll try to see if it's a Windows 10 issue or a Windows in general issue.

Link to comment
Share on other sites

I have found that the problem is not related to specific passages or anything like that.  If I am doing a study session and start entering references, it might crash (or freeze up sometimes) on the 5th or on the 20th reference I enter.  It has never happened with the verse picker, only when keying in references.  This has been a problem for me since the release of version 14.

 

It is odd that the dump above is referencing Windows 10.  I am actually on Windows 11.

 

image.png.a73faa7c1b89d25d3e068d223afa7c7f.png

Link to comment
Share on other sites

I'm still seeing these types of random crashes and freezes. Tech support attributes it to not closing Accordance or shutting down my computer everyday. But I do not recall ever having this problem before Version 14.

Link to comment
Share on other sites

Thanks for the feedback on it! I'll run some more tests.

Link to comment
Share on other sites

19 hours ago, Cnthetford said:

I have found that the problem is not related to specific passages or anything like that.  If I am doing a study session and start entering references, it might crash (or freeze up sometimes) on the 5th or on the 20th reference I enter.  It has never happened with the verse picker, only when keying in references.  This has been a problem for me since the release of version 14.

 

It is odd that the dump above is referencing Windows 10.  I am actually on Windows 11.

 

image.png.a73faa7c1b89d25d3e068d223afa7c7f.png

 

Win 10 and 11 share the same kernel version (10.0) according to the following link.

https://answers.microsoft.com/en-us/windows/forum/all/windows-11-supposedly-installed-but-keeps/d17f0819-275a-4741-a704-f7216a34024f

  • Like 1
Link to comment
Share on other sites

Adding this to my list to look into today when I'm at my Windows PC.

Link to comment
Share on other sites

I can't reproduce the crash in 14.0.6 or 14.0.7 beta, but as you said, it may be random verses that's causing it to occur, not a specific sequence. I still sent on the crash report to see if we can pinpoint it. If you encounter any more crash reports, post them here.

Link to comment
Share on other sites

Here is another one.  I just opened accordance and started entering random passages.  After 15-20 of them, the application froze (when it does this, all of the Office documents and windows explorer freeze as well until I kill Accordance with task manager).

 

Then I opened again and started entering random passages.  Again after a bunch of them, the program crashed this time.  Here is the dump.

 

This was all in ESVS with the info pane turned on.

 

Accordance Crash Log
Crashed at: 19:40:10:395 On: 13 of Jul, 2023  Central Daylight Time

Accordance 14.0.6 (14.0.6.0)
Windows 10 (10.0.22621)
RAM: 9964MB free of 16309MB total
Disc: 434GB free of 931GB total


Out of memory
Address:   $00412531

Backtrace: 
  $00412531
  $0041286D
  $0043DF63
  $00702FE6
  $0085A0D2
  $009F58D3
  $00A43C1C
  $009127CC
  $00912611
  $00914E49
  $004E177B
  $00915318
  $004E18E0
  $009057CC
  $007B4E95
  $007B4BAC
  $007B4806

Link to comment
Share on other sites

Ok.. I did another test.. here is the list of references I entered (1 at a time) including some typos because I always make them.  I have very little confidence that even with the same sequence, you will see the failure, but who knows?

 

judges 3:5
1thess 4:15
rev 12:1
mk 10:4
act 4:5
rom 5:12
1pet 3:21
rom 12:1
mic 3:4
ps 121:3
nah 2d:3
nah 2:3
mk 16:!
mk 16:1
tit 1:4
heb 7:6
jas 3:5
1chr 9:3
heb !0:1
heb 10:1
1pet 2:15
2pet 3:2
1jn 2:15
act 17:1
2cor 12:1
2tim 3:15
jun 1:!10
jud 1:10

 

Here is the dump..

 

Accordance Crash Log
Crashed at: 19:52:27:479 On: 13 of Jul, 2023  Central Daylight Time

Accordance 14.0.6 (14.0.6.0)
Windows 10 (10.0.22621)
RAM: 8842MB free of 16309MB total
Disc: 434GB free of 931GB total


Out of memory
Address:   $00412531

Backtrace: 
  $00412531
  $0041286D
  $0043DF63
  $00702FE6
  $0085A0D2
  $009F58D3
  $00A43C1C
  $009127CC
  $00912611
  $00914E49
  $004E177B
  $00915318
  $004E18E0
  $009057CC
  $007B4E95
  $007B4BAC
  $007B4806

 

Also, part of the way through the display looked like this (it may be completely unrelated, but just in case it helps)...

 

image.png.61428fde3e521583dc5f14d1ee7f22ec.png

  • Like 1
Link to comment
Share on other sites

I'll try this next time I'm on my Windows PC.

Link to comment
Share on other sites

I couldn't duplicate this. If you continue to experience these issues, you may need to email Tech Support so we can better pinpoint what's happening.

Link to comment
Share on other sites

There's no point in trying to duplicate these random crashes and freezes. They are random, hence by their very nature they cannot be duplicated.

Link to comment
Share on other sites

What I'd like to find out is if these are truly random, or if there's some form of pattern we can pick up. That would help us pinpoint what could potentially be causing the crashes.

Link to comment
Share on other sites

They are truly random.

Link to comment
Share on other sites

That's unfortunate. If you happen to ever detect some form of non-random pattern, definitely keep us posted. In the meantime, if you continue to have the random issues, you can try emailing support, and we'll try to assist.

Link to comment
Share on other sites

As I mentioned above, I did already email tech support about these random crashes/freezes. They attribute it to not closing the program and turning off my computer at the end of every day. As for the only non random, completely repeatable crash that I've been able to document. I did post a thread about that, tech Support verified it, the programmers had already prioritized it, but a fix has not yet appeared.  

Link to comment
Share on other sites

Good to know. Thanks for the update! I usually turn off my machine at the end of the day just to save power, but if it didn't happen to you before now, that is strange.

Link to comment
Share on other sites

I keep my computers on because the power savings between sleep/hibernation modes and totally off is next to nothing, and I usually don't really know when my work or leisure computing day is over. My company IT-department has advised me to generally leave my computer on, but on occasion to reboot. There are different philosophies on this, but this is a very standard position.

Link to comment
Share on other sites

I have a similar work day with my other job. :-) I used to just put mine to sleep at night, but since I have multiple machines sitting around (one a more massive machine), I thought powering them down would eke out a little more on my energy bill each month. They all reboot pretty quickly, so I can generally boot them up in the morning, and they'll be ready before I finish waking up. :-)

Link to comment
Share on other sites

So yesterday, I closed Accordance (and all my other programs) and shut down my computer completely (not sleep or hibernation mode). Turned on my computer today, started Accordance, went to two separate texts in two different workspaces. Accordance froze and crashed while trying to scroll in the second workspace. The only thing that might have been unusual, perhaps, is that when I first went to open the second workspace (Jewish scriptures), I still had a New Testament text highlighted in the first workspace so at first the second workspace would not open because the highlighted NT text (Mk 4,10-12) cannot be found in the Jewish scriptures (despite Mark's allusion to Isa 6,9-10). So I unhighlighted the NT text and the Jewish scriptures workspace opened fine. Went to Isaiah 6 and when I started to scroll through Isaiah, Accordance froze, began draining computer resources, which also caused other programs to freeze up. As is usually the case, no crash log was generated by Accordance. 

 

This crash obviously cannot be attributed to not closing Accordance and shutting down one's computer completely. Nor is it random, at least not on my computer with my specific Accordance workspaces. If an Accordance programmer or tech support wants to remote into my computer and have me repeat the exact steps, I'm happy to accommodate. 

  • Like 1
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...