Recently, my anki has been having issues with crashing whenever I open a file within anki (i.e. to upload a file for image occlusion). I initially thought that it was related to my image occlusion add-on, so I uninstalled and reinstalled it. Once issues persisted, I made sure my anki was up to date, checked files within my databases and media, changed my driver to from Direct3d to OpenGL, removed all my ad-ons to see if something else was causing the issue, and still no luck. I also checked if there was an issues with the IO in the “manage deck” open with no luck.
When I tried to open one of my back-ups to see if reverting my anki would help, but that crashed too. That lead me to believe that there is some issue with my Anki opening files within Anki and not something specifically tied to image occlusion.
I would love any help or feedback to fix this issues as soon as possible. Thank you!
I’m not a “he” – and there’s no need to link/ping me for questions. There are lots of helpful folks here, and @Anon_0000 noticed the same connection I would have.
If you don’t have an answer for someone’s question, linking them to an unrelated thread isn’t helpful. It would be better for you to just not comment.
Requiring users to provide basic information about their operating system and installed plugins is fine, but you’re ignoring it. Even the help file only mentions it in case of a crash. But code doesn’t always freeze, or freeze so severely that everything stops working, and such data is absolutely necessary, and every program collects it.
As for “they” or “she”—sorry, those are translation errors from the image… In English, animals don’t have gender unless you specifically specify it, but in our language, it’s important. So I don’t know how to address you. You can address me as “he” or “she,” as long as it’s not “it.”
Regarding the program’s responsiveness to the user: in both cases, the person asking the question doesn’t explain anything, so why should anyone have to guess what’s wrong? In such cases, I usually just remotely connect to the user’s computer and figure out the problem in 10 minutes. But these days there are too many different operating systems and devices, and it’s impossible to understand the cause of a program failure without knowing what device it is.
