• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Gaussian Blur in Photoshop CS5 Corrupting files

New Here ,
Nov 11, 2010 Nov 11, 2010

Copy link to clipboard

Copied

We just got brand new systems at work less than a month ago and this event has happened twice since then. When using Photoshop CS5 Extended and using Gaussian blur the file becomes blocky and all layers as well as their masks become corrupted with these blocks. Can anyone help or is there any advice?

Here are my system specs...

Model Name:    Mac Pro
  Model Identifier:    MacPro5,1
  Processor Name:    6-Core Intel Xeon
  Processor Speed:    2.66 GHz
  Number Of Processors:    2
  Total Number Of Cores:    12
  L2 Cache (per core):    256 KB
  L3 Cache (per processor):    12 MB
  Memory:    16 GB
  Processor Interconnect Speed:    6.4 GT/s
  Boot ROM Version:    MP51.007F.B00
  SMC Version (system):    1.39f11
  SMC Version (processor tray):    1.39f11

Christmas LIVE Ad (original).jpg

Views

61.1K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Nov 11, 2010 Nov 11, 2010

Ok, try disabling all third party plugins and try again.

After that, try disabling the extension plugins, and try again.

If this was a widespread problem, I think we'd be hearing about it from more users.

So my guess is that it is something to do with your system or configuration.

Votes

Translate

Translate
Adobe
replies 227 Replies 227
Jun 12, 2012 Jun 12, 2012

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Aug 02, 2012 Aug 02, 2012

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Aug 02, 2012 Aug 02, 2012

Copy link to clipboard

Copied

Well, we need exact steps to reproduce the problem.  It's possible that it's not the same problem at all, or may have been a one-off event due to other problems.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Aug 30, 2012 Aug 30, 2012

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Aug 30, 2012 Aug 30, 2012

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Aug 30, 2012 Aug 30, 2012

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Aug 30, 2012 Aug 30, 2012

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Aug 31, 2012 Aug 31, 2012

Copy link to clipboard

Copied

Hi Hurmeli,

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.

Thanks!

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Sep 03, 2012 Sep 03, 2012

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Sep 04, 2012 Sep 04, 2012

Copy link to clipboard

Copied

I'm still having this issue -- today alone I've lost about 3 hours of work.

The only commonality between the two issues was adjusting the levels of a layer in a group, behind a mask.

Precorruption:

Screen shot 2012-09-04 at 12.22.11 PM.png

Post-corruption (nothing recoverable, or in channels):

Screen shot 2012-09-04 at 12.21.32 PM.png

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Sep 10, 2012 Sep 10, 2012

Copy link to clipboard

Copied

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.

http://i.imgur.com/lymtch.jpghttp://i.imgur.com/kbDezh.pnghttp://i.imgur.com/MFBxr.jpghttp://i.imgur.com/2tInk.jpg

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Sep 23, 2012 Sep 23, 2012

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
May 28, 2013 May 28, 2013

Copy link to clipboard

Copied

I was wondering if Adobe considers this problem fixed? [Please see the last paragraph, where it gets interesting, as I hope it contains a clue to help figure out what's going on here.]

My company installed CS6 about a month ago and I still have this problem. I also had it with CS5.

Like everyone else the corruptions plays out as some layers having “Holes” punched into them, but mostly my Layer Masks get holes punched or get "Tiled" with images. The corruption happens when I’m running the Motion blur on a Smart Object, although it happened once when using the Gaussian blur on a Smart Object.

Last time it happened to me with CS5, even after quiting Photoshop ( I did not save my file after the corruption happened) the "Tiles" were there. I then trashed my preferences, reopened the file, then it was OK.

Now for something weird (I think (hope) this will be telling for Adobe Techs). Last week, in CS6 It happened to a file again. First time for this file. I was zoomed in when I saved so I didn't realize the corruption, that punched holes in 3 separate Adjustment Layer’s masks, till it was too late. Here is where it gets interesting. I had other files, same resolution and pixel dimensions, they also had the same adjustment layers with the same layer masks. I thought I could just copy the masks from one of these files. But to my surprise the same 3 Adjustment Layer masks had the exact “holes” punched in to them. I didn’t have these other files open when the one got corrupted--in fact, although I worked on them earlier in the day, I hadn’t touched them for a couple of hours. It’s like Photoshop thought (if it could think), “This is the same file, so my cashe tells me to punch holes into these masks”. Luckily after restarting Photoshop the other files were OK, so I could copy masks from it.

I hope this is helpful, ans please, per the first paragraph above, is there a fix I missed?

Much thanks in advance.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
May 28, 2013 May 28, 2013

Copy link to clipboard

Copied

We have not seen this problem in CS6.

The only similar things we have seen are due to other corruption (disk errors, bad RAM) or video driver bugs (which make it just appear wrong, even if the file data is OK).

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
May 28, 2013 May 28, 2013

Copy link to clipboard

Copied

Thanks for the fast reply. The IT guys here already replaced the RAM, so I'll ask them to look into disk errors and video driver bugs. Wish me luck...I'll need it.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jun 24, 2013 Jun 24, 2013

Copy link to clipboard

Copied

This problem has happened 5-6 times for me in the past week--initially on CS6, and then, after upgrading, on CC. I applied Gaussian Blur with a Wacom tablet (this is using a brand new MacBook Pro 13", very little software installed)--and my file has many elements turn black, totally corrupted without even saving it. The modules in my design all looked like the one on the right, and they were suddenly corrupted the instant I applied Gaussian blur to look like the one on the left. These were layers I wasn't even touching, and now the PSD needs to be rebuilt. Hugely frustrating.

Screen Shot 2013-06-24 at 2.43.47 PM.png

Can no one at Adobe reproduce this issue? I can confirm that it's a bug in CC as well as CS6.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jun 28, 2013 Jun 28, 2013

Copy link to clipboard

Copied

rtourtelot wrote:

I can confirm that it's a bug in CC as well as CS6.

Could it be a bug with your system, rather than a persistent problem in multiple Photoshop versions?

Do you have ECC RAM to detect and correct errors?  Redundant disks in an array?  These kinds of things exist because there actually IS the possibility of error.  And we all know that besides hardware faults, system hardware and software designs aren't perfect.  If a perfect system were available, people wouldn't buy any others.  Nothing makes Apple systems exempt from the possibility of faults.

I'm not saying your system is at fault, but I just mentioned the above because there are many, many people who don't see these kinds of problems.  Just keep in mind it could possibly be a system-specific issue.

-Noel

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jun 28, 2013 Jun 28, 2013

Copy link to clipboard

Copied

Hi Noel,

Thanks for your response. Here's what makes me think this is an Adobe PS issue: this problem has persisted for me across 3 separate laptops, on both CS6 and CC versions of Photoshop. I have no idea what ECC RAM or redundant disks are, unfortunately.

As for why many users aren't reporting this issue, I believe it's because the following factors play a role (as this is how I saw the bug in multiple cases):

1) An extremely complex PSD with many high res layers and nested groups.

2) A masked layer within a nested group.

3) Using a Wacom tablet

4) Applying Gaussian blur

For me, the instant I applied Gaussian blur under these conditions--on different machines--not only was the file I was working on corrupted in that various layers turned black, but all other open Photoshop documents were permanently corrupted. I didn't save the document I was working in, or the other documents, but all open PSDs were ruined. Nothing outside of Photoshop was affected, and I haven't seen this bug or anything like it anywhere else.

It's not the end of the world--as much as the appearance of this bug has been a huge pain for me the times it happened. I'm surprised Adobe has been unable to reproduce it, though. Just because many users aren't reporting it, doesn't mean that it's not there. Like I said, it requires certain potentially uncommon conditions, but it is nonetheless a terrible experience for those that are confronted with this bug.

Honestly, I can work around it (not use Gaussian blur, for one)... but it's just one more thing that's making me seriously consider moving to Sketch.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Jun 28, 2013 Jun 28, 2013

Copy link to clipboard

Copied

If the file was saved in CS5, then it was corrupted by CS5.

And it was only when using some filters on smart objects -- not just general GBlur usage.

But we have not seen this sort of problem with Photohop CS6 or CC.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jun 28, 2013 Jun 28, 2013

Copy link to clipboard

Copied

Chris, this is happening on brand new PSDs, never once opened in CS5 or on a computer that ever had CS5 installed on it. I can guarantee you that this is happening in CS6 and CC. I have files that were never created or opened in CS6--only CC--where I had this bug occur.

There was no smart object involved in my case. This was on a masked (non Smart Object) layer, using Gaussian blur.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Aug 01, 2013 Aug 01, 2013

Copy link to clipboard

Copied

I've been struggling with this all afternoon. I tried to step back and see what I had recently changed with photoshop, and earlier today I had installed a set of pre-made actions. I uninstalled them, reset the actions pallette, restarted photoshop. I opened up the file that had been severely corrupted before, and now it looks perfectly fine. When before, it had seemed that all hope was lost and that I would have to start over.

Before uninstalling the actions, I could replicate the problem over and over, any time I used the GB, on any file.

It's definitely a strange problem, and I hope this helps some of you out, or helps adobe track down the issue.

I'm using CC, the set of actions I installed were called "Instant Hipster" (a client wanted their photos to look like instagram, lame, i know):

http://photoshoptutorials.ws/downloads/photoshop-actions/freebie-10-instagram-photoshop-actions/

I'm on a macbook pro, using the latest verison of OSX. Maybe someone form adobe could try installing the actions, using them a few times, then try some GB in a new file? Could that help in tracking down the bug if you could replicate it?

Here's an image of what my file looked like after using GB before the problem was fixed:Screen Shot 2013-08-01 at 7.50.58 PM.png

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Aug 01, 2013 Aug 01, 2013

Copy link to clipboard

Copied

Thanks for the tip about the actions, rjlzaitz.

Adobe is not very likely to invest any resources on a version specific bug when that Photoshop version is no longer supported, though.  There will be no updates to CS5.x, and Adobe says they have not seen the bug in CS6 or CC.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Aug 01, 2013 Aug 01, 2013

Copy link to clipboard

Copied

Well, it happened in their latest version, CC. And I've noticed several other people are experiencing it in CC as well.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Aug 01, 2013 Aug 01, 2013

Copy link to clipboard

Copied

Ah, thanks for clarifying that.  I stopped at CS6.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Aug 22, 2013 Aug 22, 2013

Copy link to clipboard

Copied

I have had this problem happen in CS5 and CS6.

It just happened again today.

Almost all of the time it is due to gaussian blur, but I have had it happen with Adjustments-shadows/highlights and High Pass.

Every time it has happened with gaussian blur it was never with a smart object.

I have submitted info before to Chris and Jeanne and was never able to get a fix for this problem.

It doesn't happen consistantly and cannot be reproduced at will. It may happen once or five times in one day and then not again for 3 months or more.

It destroys layers, adjustment layers and masks.

Along with hours of work you will not get back.

here are some of the images to show the destruction.Screen shot 2012-05-11 at 11.32.32 AM.png

Screen shot 2012-05-11 at 11.21.54 AM.pngScreen shot 2012-05-11 at 11.06.45 AM.pngScreen shot 2012-03-01 at 2.02.57 PM.png

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines