Thanks for the report.
The error message seems to come from leveldown, which is a database engine.
So, it happens in the native layer.
I guess it’s nothing to do with your installed node version.
I’ll look into the clean-up part!
I can reliably reproduce this error when I update the content of a note and then close the app immediately afterwards.
This situation has been simulated for reproduction. However, the error sometimes occurs even after a longer period of time between changing the note and closing the app.
On a side note: I find it quite unusual that I get this assertion dialog. (By default, these are only shown in debug builds)
I still get the assertion when I close Inkdrop without manually saving the note or switching to another note first.
Maybe it is possible to save the note when closing (exiting) inkdrop, like it is done when you focus another application and wait until saving is finished?
Oh ok, i thought that this bump up should mean that it is included.
With “save” I have formulated this somewhat ambiguously. The note is saved locally but not synchronized.
