Rev 8.0.453 Crash Using Undo in Flood-Fill

Moderator: jsachs

Post Reply
jfoster
Posts: 198
Joined: December 1st, 2011, 1:39 pm
What is the make/model of your primary camera?: Canon/5DMIII

Rev 8.0.453 Crash Using Undo in Flood-Fill

Post by jfoster »

Attached is a workspace file that crashes 8.0.453.

I was trying out the Flood-Fill features and noticed that the mask had encroached a bit on my subject. When I tried to use Undo to roll back to the point where the unwanted masking occurred the Undo wouldn't work. I saved the workspace and tried to reproduce the problem in a test workspace but I was not successful.

When I try to reopen the original workspace file, PWP crashes.


Jeff
Attachments
80453_crash.zip
(4.26 KiB) Downloaded 35 times
jfoster
Posts: 198
Joined: December 1st, 2011, 1:39 pm
What is the make/model of your primary camera?: Canon/5DMIII

Re: Rev 8.0.453 Crash Using Undo in Flood-Fill

Post by jfoster »

After playing around, I was able to reproduce the problem in a much simpler workspace. My hunch is that is has to do with unexpected combinations of shift, control, mouse-click and mouse movement.

Attached is the simpler crashing workspace.

Jeff
Attachments
SimpleWorkspaceCrash.zip
(982 Bytes) Downloaded 36 times
jsachs
Posts: 4451
Joined: January 22nd, 2009, 11:03 pm

Re: Rev 8.0.453 Crash Using Undo in Flood-Fill

Post by jsachs »

All I can tell from the saved workspace files is that somehow the seed coordinates have become corrupted. This probably happened before you saved the workspace so I would need to know the sequence of operations you performed just before saving it.

I did eventually find a scenario where undoing a flood fill was causing problems, namely click flood fill button without setting a seed point (red Apply button is shown when it should not be), then click lasso button (PWP asks to finalize a non-existent operation - click Yes), then click mask undo. At this point Undo does nothing no matter how many times you click it. This is fixed for the next release, but that will not be until at least 10/16.

There may be other scenarios that cause problems, so please let me know if you discover anything else.

I also found a problem with Ctrl-Shift click to start a new operation which I have fixed for the next release. In the meantime I suggest no using this feature. I also added code to check for invalid seed coordinates and give an error message instead of crashing.
Jonathan Sachs
Digital Light & Color
Post Reply