I'm curious if anyone else has encountered this and if there's a way to avoid it or troubleshoot it.
Every now and then when I'm working with a file that has multiple layers (usually 20-30, some with visibility off) a visual distortion occurs that basically destroys the entire file by not only effecting multiple layers but remaining even when I backtrack through the history states. The distortion usually looks like a combination of large block grids that cut out whole segments, and blurry streaks of varying opacities, if you can imagine those things combined. Once the damage has been done the layers are permanently ruined. I have to scrap the entire file and hope the last backup copy was recent. What makes this one of the scarier bugs I've encountered is that, it seems to happen at random effects multiple layers, and once the damage has occured, is irreversable even with history.What's bizarre is every layer seems to be effected differently with some completely undisturbed while others above and beneath are ruined, with large chunks removed and blurry streaks running through.
Usually only a portion of the artwork is disturbed, as though a particular layer (visible or hidden) suddenly has a technical spasm and effects layers within it's edges only. The fact that it effects layers not even currently selected and defies history states seems to imply that this is a serious issue and not just a weird raster hiccup that would only effect the active layer and could be undone. It seems to be a general software failure of some kind since I had it happen on one file then began having similar problems on others I tried to open immediately after (fortunately the damage wasn't permanent on those files, just the one it first occured on)
I don't believe it effects previous save states so as long as I save frequently and immediately close without saving when it happens, I should be able to recover from the existing save, but the damage and extent of this, once in a while, bug is cause for concern.
has anyone else had this issue? Is there a way to correct it?
Any insight or similar stories would be appreciated. |