Crash report: Message boxes during moving layers

[dwsel]

While moving the layer on top of the stack the bad behaviour happened. It must have been some kind of unhandled exception, because there was no usual 'report error' box. Instead the stack of message box appeared after several seconds. It happened quite fast, I was more concerned about my screen filling up with message boxes so I went to process explorer with intention to kill the app rather than reading the message. The whole application crashed while killing the process.

After restarting the application it started to recover the session without asking a question. Also the replaying of events was unstoppable. I didn't want that because the session was quite long and I had intermediate saves. I've killed the application but after another restart the same behaviour happened - the only choices were either to delete Recovery folder from user data or to let the computer run for several minutes during the events replay.

[Boris Eyrich]

I will check the crash. Do you remember the text in the message boxes?

The automatic recovery of all documents after Artweaver has crashed or unexpected ended is a new feature since version 4.5 to avoid any date loss in such situations. But I see sometimes it is not wanted to recover any document thus I will add some kind of confirmation in the next major version of Artweaver.

[dwsel]

I will check the crash. Do you remember the text in the message boxes?

Unfortunately not. They were blinking quite fast.

[dwsel]

I've managed to reproduce the bug and capture the bug. It's related to
- mouse scrolling (zooming)
- moving the layer
So far it's specific to the file I'm working on (maybe it's invisibly broken?). I'll PM you with the link to the file.

P.S. Can't seem to upgrade to 4.5.2 to see if it's accidentally fixed. Should I switch channel?

[Boris Eyrich]

I can sometimes reproduce a some similar crash while dragging layers (but without the message boxes). I will check this and try to fix it with the next update.

P.S. Can't seem to upgrade to 4.5.2 to see if it's accidentally fixed. Should I switch channel?

Update should now also work from the prerelease channel.

[Boris Eyrich]

Should be fixed now with Artweaver 4.5.3.