Anki Fatal Error Message

Anki Help
1

Hello,

I was making cards in Anki, and received the below error message which said to report this on the Anki forum. I do not recall an error occurring before this one, and after closing Anki and restarting it, I ran a check database which did not seem to run into any issues. I did a few reviews, and made a few cards after without issue. Is there anything else I should do?

A fatal error occurred, and Anki must close. Please report this message on the forums.

Below is the Debug info from the notification:

Anki 25.02 (038d85b1) (ao)

Python 3.9.18 Qt 6.6.2 PyQt 6.6.1

Platform: Windows-10-10.0.26100

Traceback (most recent call last):

File “aqt.taskman”, line 144, in _on_closures_pending

File “aqt.taskman”, line 88, in

File “aqt.taskman”, line 108, in wrapped_done

File “aqt.operations”, line 123, in wrapped_done

File “concurrent.futures._base”, line 439, in result

File “concurrent.futures._base”, line 391, in __get_result

File “concurrent.futures.thread”, line 58, in run

File “aqt.operations”, line 108, in wrapped_op

File “aqt.operations.note”, line 22, in

File “anki.collection”, line 534, in add_note

File “anki._backend_generated”, line 1290, in add_note

File “anki._backend”, line 161, in _run_command

pyo3_runtime.PanicException: assertion `left == right` failed

left: 1759287084619

right: 0

2

I just want to confirm that I should just follow the steps in the troubleshooting guide, or if this particular error requires more investigation. Everything seems fine since it happened. Thanks for any input!

3

I guess the most helpful thing would be steps to reproduce. Maybe it was triggered by one of your addons (if any) and you found an edge case that caused that error. If everything else still works fine, it’s probably safe to ignore it.

Though if you find out how to reproduce, Anki or the addon developer could look at your report and solve it.

From a quick search on github in ankis repo, I cannot find any assert* calls that have left, right (or similar) as parameters. Though it might be there and I might have missed it.

2 Likes
4

Thank you for your response! It seemed to occur after making a note, although when I did the exact same things again after the error (making notes, even deleting and remaking the note that I was doing before the error), I was not able to reproduce it

My gut feeling is that I accidentally double clicked on create note, as my laptop touchpad has been having that issue. I think I saw Dae say somewhere that this could cause an error.

3 Likes
5

I managed to reproduce it. I think you’re right that it’s triggered by a double click.

Logged here: Fatal error when double clicking Add too quickly · Issue #4376 · ankitects/anki · GitHub

3 Likes
6

Thank you for taking the time to test that and add the report, I really appreciate it!

1 Like
7

Anki 25.07.5 (7172b2d2)
Python 3.13.5 Qt 6.9.1 PyQt 6.9.1
Platform: Windows-11-10.0.26100-SP0

Traceback (most recent call last):
File “C:\Users\Bles\AppData\Local\AnkiProgramFiles\.venv\Lib\site-packages\aqt\taskman.py”, line 148, in _on_closures_pending
closure()
~~~~~~~^^
File “C:\Users\Bles\AppData\Local\AnkiProgramFiles\.venv\Lib\site-packages\aqt\taskman.py”, line 88, in
lambda future: self.run_on_main(lambda: on_done(future))
~~~~~~~^^^^^^^^
File “C:\Users\Bles\AppData\Local\AnkiProgramFiles\.venv\Lib\site-packages\aqt\taskman.py”, line 111, in wrapped_done
on_done(fut)
~~~~~~~^^^^^
File “C:\Users\Bles\AppData\Local\AnkiProgramFiles\.venv\Lib\site-packages\aqt\operations\_init_.py”, line 123, in wrapped_done
future.result()
~~~~~~~~~~~~~^^
File “C:\Users\Bles\AppData\Local\AnkiProgramFiles\python\cpython-3.13.5-windows-x86_64-none\Lib\concurrent\futures\_base.py”, line 449, in result
return self.__get_result()
~~~~~~~~~~~~~~~~~^^
File “C:\Users\Bles\AppData\Local\AnkiProgramFiles\python\cpython-3.13.5-windows-x86_64-none\Lib\concurrent\futures\_base.py”, line 401, in __get_result
raise self._exception
File “C:\Users\Bles\AppData\Local\AnkiProgramFiles\python\cpython-3.13.5-windows-x86_64-none\Lib\concurrent\futures\thread.py”, line 59, in run
result = self.fn(*self.args, **self.kwargs)
File “C:\Users\Bles\AppData\Local\AnkiProgramFiles\.venv\Lib\site-packages\aqt\operations\_init_.py”, line 108, in wrapped_op
return self._op(mw.col)
~~~~~~~~^^^^^^^^
File “C:\Users\Bles\AppData\Local\AnkiProgramFiles\.venv\Lib\site-packages\aqt\operations\note.py”, line 22, in
return CollectionOp(parent, lambda col: col.add_note(note, target_deck_id))
~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
File “C:\Users\Bles\AppData\Local\AnkiProgramFiles\.venv\Lib\site-packages\anki\collection.py”, line 533, in add_note
out = self._backend.add_note(note=note._to_backend_note(), deck_id=deck_id)
File “C:\Users\Bles\AppData\Local\AnkiProgramFiles\.venv\Lib\site-packages\anki\_backend_generated.py”, line 1429, in add_note
raw_bytes = self._run_command(25, 1, message.SerializeToString())
File “C:\Users\Bles\AppData\Local\AnkiProgramFiles\.venv\Lib\site-packages\anki\_backend.py”, line 160, in _run_command
return self._backend.command(service, method, input)
~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^
pyo3_runtime.PanicException: assertion `left == right` failed
left: 1762074374316
right: 0

8
  1. What do you do before those crashes occure?
  2. What are the steps to reproduce?
  3. Does Troubleshooting - Anki Manual help?
9

This was fixed when it was reported last month, but it hasn’t been released yet.

10

Is it the same though? The lines between those error reports are different, including the value for left.

(I can see that it’s similar, but it’s weird that the stack trace differs in the actual code lines, making me think it might be a different issue)

11

I get similar error text as the one posted by @meramera if I run the code I posted on the issue, so I think it’s the same issue, but OP got a different text for some reason (might be because he is on an older version).

1 Like
12

That’s what I was assuming. The line-by-line errors all seem the same, despite the newer formatting.

13

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.