Gaussian Blur in Photoshop CS5 Corrupting files

This has happened to us 4 times now on different files and different macs the second time I phoned up Adobe support and was told to delete the photoshop preference. Which worked for a bit but then it happened again. It does seem to have a link with the gaussian blur but other than that, it can happen to anyone on any file? It just takes block chunks from the image changes colours etc..

The studio are looking for answers and i can only dump preferences, replace from backup if there is a saved file as there seems to be little on this subject of corruption.

The updates have done nothing to address the problem.

Come on Adobe? If you want any files let me know I can give you some..

Rob

Just got the issue again today. I've been working all day on a document with around 200 layers, and many groups. It's a template document for several trading card designs.

I used the Gaussian Blur filter several times already today very successfully, but on my most recent attempt the filter instead deleted most of the data from the layer I was working on, as well as the data from all of the other layers of which that layer was a copy.

Specifically, I was producing a background texture - or rather modifying the color of a background texture I'd used in several other layers. The original layer was simply a layer that I filled with a color from my swatches (via cmd + delete) and then added a layer style for a certain pattern that I use as a background texture (a custom pattern).

I wanted to modify this pattern to a darker color instead of the light tan that it is, so on the particular layer I was working on (which is a copy of the original I just referred to) I filled it with my new darker color (again cmd + delete), turned off the layer styles after I realized my pattern was still on, and then set the swatches to two colors that are close but one slightly darker and the other slightly lighter. Then I ran Filter > Add Noise, set to about 10% Gaussian. I then ran Filter > Blur > Guassian Blur at .5 px. Next I created a layer below, filled it with the base color, and set the layer above it to about 65% opacity. Then I merged the two layers together, and attempted to run the Gaussian Blur again.

That's when Photoshop deleted all (or most) of the data from that layer, and random bits of data from other layers. It also seems to have deleted all the raster data from the other background layers which were similar to that original one I copied it from, as they are all transparent too.

I'm getting this same issue - or a similar one. It seems to only happen when I run the Gaussian blur command, and during the same process in my workflow. It also seems for me to happen when I have made a selection from a layer above that is a smart object.

Let me describe the scenario that I have experienced a couple times in the past week. (BTW I just upgraded to CS5 only a couple weeks ago).

Usually I have a document open with dozens or hundreds of layers. The effect that I am executing when this seems to happen is where I have a group of shapes or placed image smart object layer and I'm creating a shadow layer by making a blank layer below said group or image, making a selection from the above group or image, and then filling the selection in the blank layer with a color - which I then run the Gaussian blur filter on, and afterward warp transform to get my realistic looking shadow effect.

But the problem is in seemingly random instances and on seemingly random documents when I run that Gaussian blur, Photoshop freaks out and craps the bed. And by craps the bed I mean deletes pixel data from multiple layers in my document very randomly, and also generates odd bright colors all throughout the document.

You can see the initial freak out in this screen shot from when I just initially selected the Gaussian blur filter from the menu (but had not yet even clicked "OK"): http://cl.ly/3KTx . The strange thing is that I had just run this series of steps on the above layer which in the screen shot you'll see as "Layer 44", and all was well.

Here's a screen shot showing the file after I closed it out, restarted Photoshop, and opened the file back up: http://cl.ly/3K2C . In case you can't tell, data from several layers all over the file is missing and corrupted.

I'm sure I don't have to explain how exasperating this is, as this represents more than a year's worth of work on a client project, no joke. Fortunately I'm mostly done with the actual site build, but that makes the loss of the artwork files of no less consquence - especially seeing as how I'm not ACTUALLY finished and I did in fact need all of that data to complete the project.

Anyhow, some additional details which may or may not be related to the issue:

- The issue seems to happen randomly. As stated above the same steps did not produce the error just a few minutes before.

- I have had this issue with another file this week where I was doing the same processes on another shape.

- It seems that this is occuring when I make the selection from a layer that is a smart object of some type

- I also noticed artifacts in the weird colors (after I tried running the processes again, so not in the above screenshot) that were actually design elements from an entirely different document that I was working with earlier this evening.

- I have filed a bug report.

Dunno what else to describe, but I hope you guys can get this figured out, seriously. I paid way too much for my upgrade to CS5 to have bugs in key software features corrupt my files thank you.

Also, in regards to my system...

  Model Name: Mac Pro

  Model Identifier: MacPro4,1

  Processor Name: Quad-Core Intel Xeon

  Processor Speed: 2.26 GHz

  Number Of Processors: 2

  Total Number Of Cores: 8

  L2 Cache (per core): 256 KB

  L3 Cache (per processor): 8 MB

  Memory: 16 GB

  Processor Interconnect Speed: 5.86 GT/s

  Boot ROM Version: MP41.0081.B07

  SMC Version (system): 1.39f5

  SMC Version (processor tray): 1.39f5

Chipset Model: NVIDIA GeForce GT 120

  Type: GPU

  Bus: PCIe

  Slot: Slot-1

  PCIe Lane Width: x16

  VRAM (Total): 512 MB

  Vendor: NVIDIA (0x10de)

  Device ID: 0x0640

  Revision ID: 0x00a1

  ROM Revision: 3386

  Displays:

Display Connector:

  Status: No Display Connected

LED Cinema Display:

  Resolution: 1920 x 1200

  Pixel Depth: 32-Bit Color (ARGB8888)

  Main Display: Yes

  Mirror: Off

  Online: Yes

  Rotation: Supported

  Connection Type: DisplayPort

I haven't seen that before, but it looks a bit like an OpenGL drawing issue.

Could you try disabling OpenGL drawing in preferences, restart, and try again?