OK, seems to have been fixed in the alpha version, we'll see if it happens again.
Basically fixing the crash in the image object handling from the first log, fixed the issue altogether as it seems for now.
Image object handling on the image page will be much more robust in the next public update, regardless that I could not replicate.
Basically fixing the crash in the image object handling from the first log, fixed the issue altogether as it seems for now.
Image object handling on the image page will be much more robust in the next public update, regardless that I could not replicate.