Thank you very much for your report. I'm aware of a crashing bug and will release a new version soon.
Like what you describe, the problem happens just after updating the movie database, and the error message looks the same. The explanation is that after hot-swapping the old and the new databases, some variables are still tuned to the old database. The program ends up in a state where it crashes easily, but after a restart (or a crash) everything is fine again.
Drift wrote:
After today's update, I relaunched Coollector and was greeted with a warning.
I'm puzzled by the chronology you describe. Are you sure it happened in that order?
Did you update only the movie database, or did you update the whole app?