This makes no sense. The value of a note has absolutely no relation to saving the notes, there is no possibility it can see this, that's just data. There must be something else specific to your system, but I have no idea what that could be. Why are you saying you cannot save? Wat happens when you try? Can you see any messages in Console.app? (You may need to search for net.sourceforge.skim-app.skim and choose Include Info/Debug Messages from the Action menu.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The crash report really looks like a bug in the system, as it crashes in an internal document saving method. Unfortunately the bug is too generic to say point to a reason. Does it matter what name your file has?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I get the impression that the real problem is that the save methods are called repeatedly in a loop. We certainly do not do this, we only call the passed in callback after saving, which certainly should not save again. This looks like a bug in the macOS 11 system code. But I have no way of reproducing it, so I also have no idea what triggers it. It does not look like anything we could fix, but rather something Apple needs to fix. Unfortunately it is too indirect to be able to file a bug report with Apple.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I also run into this bug in macOS 10.15 Catalina (macOS 11 Big Sur) and different pdf files before, and lost a lot of notes. I am a heavy Skim user, in my experience, this bug doesn't happened at low frequencies. ╮(╯Д╰)╭. I attach the file beblow, hoping you can reproduce it or it is just my personal situation all the time.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have no problems with saving this file. I really think there must be something wrong with your system/disk, perhaps a permission problem. Otherwise there should have been many more reports like this, but you're the only one.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This makes no sense. The value of a note has absolutely no relation to saving the notes, there is no possibility it can see this, that's just data. There must be something else specific to your system, but I have no idea what that could be. Why are you saying you cannot save? Wat happens when you try? Can you see any messages in Console.app? (You may need to search for net.sourceforge.skim-app.skim and choose Include Info/Debug Messages from the Action menu.)
The crash report really looks like a bug in the system, as it crashes in an internal document saving method. Unfortunately the bug is too generic to say point to a reason. Does it matter what name your file has?
I get the impression that the real problem is that the save methods are called repeatedly in a loop. We certainly do not do this, we only call the passed in callback after saving, which certainly should not save again. This looks like a bug in the macOS 11 system code. But I have no way of reproducing it, so I also have no idea what triggers it. It does not look like anything we could fix, but rather something Apple needs to fix. Unfortunately it is too indirect to be able to file a bug report with Apple.
I also run into this bug in macOS 10.15 Catalina (macOS 11 Big Sur) and different pdf files before, and lost a lot of notes. I am a heavy Skim user, in my experience, this bug doesn't happened at low frequencies. ╮(╯Д╰)╭. I attach the file beblow, hoping you can reproduce it or it is just my personal situation all the time.
I have no problems with saving this file. I really think there must be something wrong with your system/disk, perhaps a permission problem. Otherwise there should have been many more reports like this, but you're the only one.