Hello - i dont belive Flash is the problem. I´ve seen the issue on 2 different machines, both without flash on it.

and again! I hate it so much

here the links:

the corrupt one

http://dateien.dtpwork.de/13_corrupting_photoshopfiles/multidataWR3_of fen_Sch.jpg

how it should looks like

http://dateien.dtpwork.de/13_corrupting_photoshopfiles/multidataWR3_of fen_Sch2.jpg

MacPro, OS X 10.6.8 fully updated with CS 5.5. I have 6 Displays connected with 3 VideoCards

I can confirm it happens on the CS6 Beta.

I've never had dropbox OR Timemachine running, FWIW.

I can report that I've seen it with CS6 too (corruption knocking blocky 'holes' through mutiple layers). On a late 2011 macbook pro. Was NOT using Gaussian Blur at the time.

No I'm not.

The corruption was identical to types displayed on this thread and files I've seen before. And it is not just being caused by Gaussuian Blur. This page of the thread alone has two cases of corruption from other causes (posts 162 & 156). I'm sorry I can't give more info but I was working on a freelance mac at the time.

Data corruption - inappropriate data written in tile-like fashion into one or more image planes - would look like what's being described here.

Chris, given your comment your mindset may be that you suspect something in the implementation of the Filter - Blur - Gaussian Blur function is causing it.  I suspect that this is not that kind of problem, but that the failure is only indirectly related to Gaussian Blur.

For example, what if it's a pointer getting screwed up and data being written into image planes where it's not supposed to go?  I could imagine that display driver glitches (or, indeed, glitches in any other part of any code running in the process) could cause such a thing to happen anywhere in Photoshop's memory space.  I've seen OpenGL implementation problems do exactly that, and the problems just vanish with a display driver update and no other changes to the code.

Around the time of Windows 7's initial release, I fought for months a problem where using a specific pen with a specific pattern was causing the GDI code to write data randomly into my address space.

My point is that the root cause could be anywhere (and could even be multiple root causes).  Everything has to work perfectly, including the drivers and the operating system, all the time to avoid data corruption.

The real reason for something like this and other persistent multi-version problems (such as the Help popping up) could be that the general memory management structure of Photoshop, or even of an executable in general, allows such corruption.

-Noel

Ugh. I hate to be the bearer of bad news, but I just got it on a brand new Macbook Air 2012, running OSX Mountain Lion, and on Photoshop CS6 (not extended).

And this time, it wasn't Gausian blur that was the culprit, it was the Add Noise filter.

Completely deleted all the raster content from one layer that simply had raster content (which I had run the Add Noise fill on earlier, strangely enough). And screwed up the mask on another layer (a fill layer), but fortunately for that layer when I deleted the layer mask it was fine (guessing because it wasn't a raster layer, but rather a fill layer).

Sad part is, I haven't had this issue happen in well over a year I think.

Bummer.

I just had this happen to me again. It's been few months since the last time.

I had a webpage layout open in photoshop. Complicated, lots of layers, around 1600x1200 pixels in size. I decided to make a new iteration of the old layout and duplicated the image. The old layout was left open in the background.

I made few changes in the new layout and then I used gaussian blur on one layer. Everything got corrupted. I wasn't worried yet because I hadn't changed that much so I just closed the file with out saving at all. Now the old layout is visible for me and I notice it has gotten corrupted as well. Random square crap on every single layer and channel.

So I close the file with out saving. Then I open it up.

The corruption is still there.

I close it again, quit photoshop and open the file again. Now the corruption is gone. But if I had closed photoshop and saved the file accidentally without noticing it was corrupted I would have lost days worth of work. That old layout was the backup and normally it would never get any changes done to it nor would it get saved.

Alas I cannot remember the exact steps I did but here is what I remember:

1) Transform to resize a layer from 1600px to 990px wide

2) Edited a mask

3) Used Gaussian blur on the layer itself

It's just a hunch so perhaps it's useless but I think every time this corruption has happened to me I've edited a mask at the time of corruption or right before it.

Mac OS X 10.6.8

Photoshop CS 5 12.0.4

Please get something done, this has been going on for years now. How about you find out what's causing this instead of popping out yet another version of CS in the future? Adobe Photoshop is an incredible product but unfortunately it has no alternatives.

I f***ing got it!

I was missing one step and also found out that I don't have to touch the mask, but I can now re-create the corruption again and again.

I always closed Photoshop between tries so the corruption doesn't remain in memory.

Open up same file as before (obviously never actually save it between tries).

Rough setup of the layers I was actually editing (the file had dozens of other layers but I never touched those):

Layer 1 (with mask) Fill 30%

Layer 2 Fill 30%

Both layers had the same photograph on them. Layer 2 had already had it blurred before. Both layers have blend more set to Color dodge.

1) Select both layers

1) Transform both layer (1606, something px to 990px with aspect ration maintained)

2) Change Fill opacity of Both Layers from 30% to 20%

3) Use Gaussian blur on layer 2 (used 20px setting myself)

Sometimes the corruption happens with the gaussian blur preview, sometimes you actually have to click Ok and apply the blur before it hits.

I've tried it six times now and only once it didn't corrupt the image.

Other people should probably try something similar. It's possible not all steps are necessary. But I never got the corruption when:

1) I didn't transform

2) I didn't change fill value

3) I didn't have mask on one of the layers

So there, I hope that's going to help someone over Adobe. I can experiment more later on but right now I need to get some actual work done so I'll get back to it later on.

And I was so hopeful I had gotten onto something.

I'll download and try CS6 trial here at work when I got some time, hopefully tomorrow.

Hi all -

I had my company purchase Photoshop CS6 for me, and i'm STILL having these issues.  I'm happy to post an entire PSD if that'll help, but for now, attached are more screenshots of corruption across ALL channels, and most masks.

Again, adjusting levels of a layer behind a mask, and again, I'm unable to reproduce it.