Random permanent layer damage!

  • 1
  • Problem
  • Updated 6 years ago
This is a BIG one.

First of all, good luck trying to reproduce this because not only am I 90% certain it only happens when working switching between CS5 and CS6 and working on the same file (which I do constantly), but there also appears to be no pattern of occurrence. I can't make it happen. Nor can I make it NOT happen!

Photoshop is randomly corrupting small portions of layers . . . quite randomly. See below.

___

EXHIBIT 1
A prominent example: http://i.imgur.com/bq3xJ.png

This image is of a bunch of obnoxiously colored vertical bars illustrating how a website's grid is laid out. Zoom in and check out all the random noise. Permanent damage. They should all be clean vertical continuous columns but they're now riddled with junk. Both color AND opacity have been altered in the affected pixels.
Now what if those layers were important photographs or something? It's all easily fixed, fortunately.

___

EXHIBIT 2
Another example. A little worse this time. Poster design thumbnail has been corrupted with random purple backbuffer garbage looking noise:



___

EXHIBIT 3
It even affects text layers. In this case I can fix it by editing the text layer:

When I edit the text layer, Photoshop stop using it's "corrupted" cached pixel preview of the text layer and redraws it, so this fixes it.

I never know what corruption I may find each time I open the file in CS5 or CS6.

I've had this happen in other files, but all three above screenshots above were taken from the same file. It has ~600 layers.
Photo of mathias

mathias

  • 140 Posts
  • 13 Reply Likes

Posted 6 years ago

  • 1
Photo of christoph pfaffenbichler

christoph pfaffenbichler, Champion

  • 1199 Posts
  • 159 Reply Likes
OS, GPU ...?
May I ask why you switch between CS5 and CS6?

Boilerplate-text:
Are Photoshop and OS fully updated and have you performed the usual trouble-shooting routines (trashing prefs by keeping command-alt-shift/ctrl-alt-shift pressed while starting Photoshop after making sure all customized presets like Actions, Patterns, Brushes etc. have been saved and making a note of the Preferences you’ve changed, 3rd party plug-ins deactivation, system maintenance, cleaning caches, font validation, etc.)?
Photo of mathias

mathias

  • 140 Posts
  • 13 Reply Likes
Apologies - I should've included all this info in the OP. Any bug report is incomplete without it. I'll get it asap.

Why I switch? A fair question - I have different software at home than I do at the office. Not fun, but that's the way it is.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 765 Reply Likes
Bad RAM could cause corruption like that, and sometimes bad CPUs.
Other than that, the only thing I know of is a bug in CS5 that could corrupt data when using smart objects with smart filters and a non-blank filter mask.
Photo of mathias

mathias

  • 140 Posts
  • 13 Reply Likes
Thanks, Chris. Both machines are very new, and also rather high-end, so while I doubt it's hardware imperfections at fault, it's still possible I suppose.

Also, the affected layers were never smart objects, neither actual smart object layers or normal layers inside of a smart object. That I can recall anyway. My posted "exhibits" aren't smart objects anyway.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 765 Reply Likes
New doesn't mean that the hardware doesn't have defects. Just keep an eye on it.

If no smart objects with filters and masks were involved, and you're not running beta builds or other damaged binaries -- then my bet would be on hardware problems.