I am not able to reproduce this. I suspect it’s a video driver issue, and you may be able to work around it by choosing software mode: Display Issues - Anki Manual
used Qt5, and the issue cannot be reproduced there…
Qt6 installation:
immediately after installation, the issue cannot be reproduced
however, when i closed down anki, and launched it again, the issue returned. extremely odd
this is unfortunate, because my pc is quite a high end one, and I thought it would be able to handle an SRS app :/.
given that the issue continues to occur regardless of the fact gldriver6 is set to auto or software, and given that the issue does not occur in Qt5: Could it be Qt6 that is the issue? because i simply cant see why my pc wont handle anki when it has handled software and games that are way heavier and more demanding
also, if you follow the following steps, anki will not crash:
open Anki
click on a deck to study
click on Study Now
open the Stats window (which shows your profile statistics)
scroll down to the bottom of the screen
click on one of the Added graph bars
browser will open
close the stats window
close the browser
Anki is doing fine!
Now, if you repeat the steps i initially posted, anki will crash again!
is there a debug mode to capture what is going on?
Those steps do not trigger the issue for me. It is quite possibly a bug in Qt that is timing-dependent, and your computer may just fast or slow enough to trigger it.
Thank you dae! if there is anything else i can do to help resolve this issue, let me know!
i dont really use python, but if you would like me to do some live debugging and testing with the assistance of a developer, then i am happy to do that
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):
delete history from the database
open the profile which had the crashes
do the crash-inducing steps i have outlined above
no crash!
However, if you do the following, you will get a crash (CRASH steps):
delete history from the database
open the profile which had the crashes
Check database and wait for it to finish
quickly press T to get Stats
close Stats (Esc)
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):
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.