Anki crashing after opening stats window - Exception code: 0xc0000005

A new issue development

so i created a new profile in anki 2.1.52-qt6, and i have tried the steps i outlined above. there was no crash!

the crash was only occuring with my OLD profile (i.e. the profile which i had since the beginning).

however, when i exported the content (i used both types of export) from my OLD profile to my NEW profile, the crash started to occur again.

in summary, the crash does not occur on an empty/small profile. CORRECTION: the crash does not occur on profiles that have small/no repetition data (I have import a deck with 13k cards and no rep history. the crash did NOT occur)

i can now confirm that the crash does not occur (kind of) if you have a small/no repetition history.

steps i have taken (no crash steps):

  1. delete history from the database
  2. open the profile which had the crashes
  3. do the crash-inducing steps i have outlined above
  4. no crash!

However, if you do the following, you will get a crash (CRASH steps):

  1. delete history from the database
  2. open the profile which had the crashes
  3. Check database and wait for it to finish
  4. quickly press T to get Stats
  5. close Stats (Esc)
  6. crashed!

I don’t know whether you used empty profiles or not, but perhaps, what you can do in order to reproduce the issue is (unless you have already done that):

  1. download a relatively large deck (say 13k cards. you can use Brosencephalon.com — Brosencephalon Flashcard Decks & Collections)
  2. reschedule all of the cards (using shift+ctrl+d from the browser)
  3. close anki and delete all of the database rep history of that profile
  4. open anki and choose the profile you have just cleaned
  5. Check database and wait for it to finish
  6. after that’s done, quick press T to get Stats
  7. close Stats (Esc)
  8. you should expect a crash. if not, then repeat steps 4-8 again (after restarting anki)

sorry post is slightly incoherent. let me know if anything is unclear

I have experimented with different collection/history sizes and even tried adjusting the code to alter the timing, but still have not been able to trigger the crash on machines here.

Let’s continue this on Crashes with 2.1.52 / 2.1.53rc

issue fixed in latest release. thanks dae!

(you can close this thread now since everything has been sorted out)

1 Like