This is driving me crazy. Like others I've been saving multiple versions of layered files, but I just lost a couple hours work on a file I've been working on for many days - I was only about 10 minutes from completion! Aargh. It occurrs randomly when applying gausian blur to regular (or any) layer. I have no 3rd party plug-ins or utilities installed with photoshop. Using CS5 on a Mac Pro4,1 (Quad-Core Intel Xeon) running OS 10.6.8. This has been going on for about a year. Totally bites.
and again! I hate it so much
here the links:
the corrupt one
how it should looks like
MacPro, OS X 10.6.8 fully updated with CS 5.5. I have 6 Displays connected with 3 VideoCards
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.
The corruption showed here looks like any kind of image corruption - including video card driver bugs.
If it doesn't involve GBlur / USM / HighPass applied as a Smart Filter - then it belongs in a different topic so we can figure out what you're seeing.
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.
Yeah, I found something while writing CS6 that looked like it may have caused the GBlur problem with smart filters -- but the required fixes were way beyond dot release size, and needed several months of testing. Yeah, it was a pointer/cache getting reused a little too often (when it shouldn't have been, and far from obvious). It didn't seem to cause problems outside of image data, but could cause image tiles to get corrupted when the smart filter recalculated.
We know we have some bugs due to OS routines corrupting the heap randomly -- there's just not much we can do about them other than begging the OS vendors to fix the bugs. (it's not even in avoidable code, so we can't work around them) But for our own code we do a lot of testing to identify and fix memory corruption, memory leaks, etc.
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.
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 just made a new duplicate of the image again.
Then I repeated my steps.
1) Quickly brushed on a mask
2) Deleted the mask
3) Transformed layer
4) Used Gaussian Blur
It got corrupted again.
Unfortunately when I repeated the exact steps second time it did not happen again.
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.
Well I had to run one more test and it worked. I can now corrupt any image open in photoshop.
1) Copy random image from net (Mine was 2000px wide or so)
2) Paste it into new document
3) Duplicate the layer (So at this point you have background, layer 1 and layer 2)
4) Grab selection from RGB channel and use it to create a mask on the top most layer (Just to get a complicated mask fast)
5) Select both layers
6) Transform them, I reduced them in size by 60% or so
7) With both layers still selected reduce their fill
8) Select the bottom layer
9) Gaussian blur
10) Enjoy your corrupted file
Try it out and let me know if it works for others as well.
I tried to reproduce this again using your exact steps, and was unable to see any corruption. As you can see from this thread, it appears to be very machine-specific. Meaning that some people can reproduce it regularly on a particular machine, and some of us can't reproduce it at all, even using the same files and steps.
We have had reports that the problem is fixed in CS6 (see Chris's post above for more details), and some have even reported that images that were corrupted in CS5 now open correctly in CS6. Since you can regularly trigger this error, you might try downloading the CS6 trial and seeing if you can reproduce it there. This would be very helpful to us to see if there's still something we need to fix.
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.
Hi all. New to the forum, but have been following this thread very closely, as I too have been having these corruption problems since I moved to PSD CS5 (and currently on CS6 - which still has these corruption errors) Now, I preface this with the fact that I'm no expert and I could be totally wrong here, but just maybe my recent experiences can help the experts chime in and maybe run with it.
I run PSD CS5/CS6 on a Mac Pro 2010 (OSX 10.8.2), 12-core 2.66 Ghz Xeon with 32MB of 1333 Mhz DDR3 ECC RAM. (OWC RAM, not original Apple RAM)
Previously, I had a lot of corruption problems (similar to those on this thread) while working mostly on large files w/ lots of layers & masks (but not always), when using brightness/contrast, hue/saturation, gaussian blur, & motion blur. As long as I didn't save the file after corruption and restarted PSD, it would revert to the non-corrupted file. However, if I saved the corrupted file, after restart of PSD, the file would remain corrupted.
Lately, I haven't been running into any problems with corruption (knock on wood), and this is what has changed since:
-I've been paying a lot of attention to my Activity Monitor, making sure that while I'm working in PSD, that I don't use up all my "real" memory, causing any page outs, essentially trying to stay away from using any virtual memory at all.
-I've noticed that in order to avoid page outs, I would have to purge my inactive memory quite frequently, as a lot of the time, the system would hold a large amount of inactive memory
maybe this corruption issue has something to do with PSD CS5/CS6 accessing Mac's virtual memory? the corruption seems to only be occurring when I get page outs on my RAM. Maybe that's why this problem is not consistently replicated since RAM status is constantly in flux and it could be a whole host of functions that thus cause the corruption? Maybe this is why when you restart PSD, that the corruption goes away (as long as you didn't save the corrupted file), since you're essentially purging out some RAM usage that might have been "held" by the previous session of running PSD?
anyway, hope this helps? (worth a shot) and if I find this hypothesis incorrect, I'll update.
Europe, Middle East and Africa