Tim Wilson

Hello, This problem is originating in a different add on, Suggest_Starting_Ease_for_the_decks_options_group. A simple solution would be to disable that other add on. Especially since this one is doing so much...

That's weird. This add-on only does stuff when you answer a card or sync. Otherwise none of its functions are accessed, so that makes no sense. So you can remove...

What kind of machine are you running on? This sounds like really poor performance for operations that take ~0.5s on my machine which isn’t even that fast (dual core 2.5GHz...

In your anki add ons folder you’ll find a folder for AnkiHabitica. In there you’ll find log files like AnkiHabitica.log[.x]. Close Anki, erase all the log files, then open it...

Since everything is timestamped, I expect we’ll be able to see what the problem is pretty easily.

This is much less of a pain than it sounds. Just move the contents of the Anki addons folder somewhere else with the exception of the AnkiHabitica.py and AnkiHabitica folder....

Please post some logs (see above) so that we can get a better idea of what’s happening.

OK, so it’s the counting of finished decks that’s doing it: 2017-02-01 10:53:13,080 [ MainThread: db_helper.py: 119 - decks_count()] DEBUG: Begin function 2017-02-01 10:53:41,664 [ MainThread: db_helper.py: 197 - decks_count()]...

Could we call decks_count() in a new thread and just have it update the score once it finishes? It would result in you getting the points for completing a deck...

All the DB stuff is read only. Should be able to do that anytime as there’s no thread locking with SQLite. Worst case scenario is that a DB query misses...