Skip to main content
Participant
November 11, 2010
Answered

Gaussian Blur in Photoshop CS5 Corrupting files

  • November 11, 2010
  • 34 replies
  • 68750 views

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

    This topic has been closed for replies.
    Correct answer Chris Cox

    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.

    34 replies

    krispykristi
    Participant
    October 14, 2017

    I just ran in too the issue the other day. I was following a youtube tutorial on how to add drop shadow/ 3d effect to typography.

    Link to youtube video: Photoshop Tutorials - How to make 3D text - YouTube

    I also was using a smart object and i too used gaussian blur alot before the issues really seemed noticeable.

    August 3, 2012

    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.

    Chris Cox
    Legend
    August 3, 2012

    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.

    Participating Frequently
    August 30, 2012

    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.

    Participant
    February 22, 2012

    For those people who cant understand why this hasnt been sorted, this is a problem affects a very small percentage of people and in order for Adobe to figure out the problem someone needs TO BE ABLE TO RECREATE THE PROBLEM, but no one can.

    From my point of view the corruption seems to be totally random. We've had it happen on 5 machines out of 15. It has reoccured on 2 machines a few times in the last 6 months but thats it. We're packaging designers so layers, masks and blur are things we use every day. From our point of view there seems to be no logic to why it happens.

    For this reason you cant really change your work flow to avoid it, the incidents we've experienced are months apart. The only thing you can do is save a copy every now and a again so you dont lose a whole days work.

    The common elements seem to be guassian blur and a few layers with masks. I have a feeling that has something to do with the machines being used as in the majority of cases it doesnt affect a whole company or if it does I bet thet bought their machines at the same time.

    Lastly once it happens thats it, there's no way back, make a cup of coffee and except the reality that your going to be redoing work you've just done.

    Adobe Employee
    February 28, 2012

    All we know at this point is that it only happens on Mac, only in CS5/5.1, and only to a small percentage of people. It does seem to be related to certain machines somehow, but so far there isn't a specific thing that all these machines have in common (that other machines don't).

    One more question that I don't think I've asked yet -- when applying Gaussian Blur, are you applying it as a Smart Filter, or just to regular layers?

    Participating Frequently
    February 28, 2012

    On a regular layer so far.

    Participant
    February 14, 2012

    Hi. I am having the same issue. My job requires that I use Gaussian blur on a daily basis. I do use a Wacom tablet, and will generally have Firefox open when working. I use a Mac, and only have the Camera Raw plug-in. I have run all the software updates, cleared my PRAM, etc etc, and am still experiencing the same issue. As with everyone else, it doesnt happen on every file, however (as a someone previously posted) my file does have a layer mask, folder(s), and use of the Gaussin blur. If we could set up a Connect session that would be great. Please let me know how to proceed. Thanks!

    Participant
    February 21, 2012

    I am pretty disappointed in Adobe for not fixing this problem, or even responding to my post. I have sent direct emails to the people that I was directed to in the forum and never so much as got a "thanks for contacting us" email. This problem has interupted my work flow considerably, and now I've spent all morning on the phone with tech support who seems to have no clue as what I'm talking about. I've offered to send them the file and got placed on hold for another 15 minutes to see if they could take the file. This problem is costing time and money, and Adobe doesnt seem to care. I can't for the life of me figure out why this hasnt been fixed... I'm going to have to go BACK to CS4. VERY DISAPPOINTED!!!!

    Noel Carboni
    Legend
    February 21, 2012

    Can we hear from Mac users who use Photoshop CS5 and DON'T see a problem with Gaussian Blur? 

    In all the posts upon posts in this thread I don't get a good feeling for whether this occasionally affects everyone to some extent, or just a select few.

    -Noel

    julstx
    Participant
    February 12, 2012

    MAC OS X 10.6.8

    PS CS5 EXTENDED Version 12.1

    Intuos 4

    No Add-ons

    Is there a reason why this hasn't been rectified by Adobe yet?  This should be escalated to upper management since it's been months.

    Is it possible that since Bridge, or associated program which converts images from 300 to 72 is affecting the quality of images?  This is one change that the older version of Bridge did not do - correct?  I noticed this when upgrading from CS3 to CS5.  Files that had not been used recently were converted to .72!!!!!!!! I WAS SHOCKED!!! NOT GOOD!  How could it ever convert back fully and at top quality?  How about this Adobe, allow the end user to determine whether they want images to convert or not at any point in work flow.  DO NOT CHANGE OUR FILES ORIGINAL IMAGE QUALITY.  Anytime I design products, it always is at 300, unless saved for WEB.

    ***  Could it be that when opening files from Bridge there is a conversion issue?  *** 

    I design digital elements and noticed that a .300 .png image got blurry all of a sudden.  I did transform it a few times.  However, this is what PS is supposed to do.  I deleted and reopened several elements to replace the blurred ones and for a personal layout, left well enough alone, there was MORE than needed to be changed.   We should not be losing visible quality while working with our files.  Consequently, I don't feel that the blurring of images has everything to do with guassian blur.  Unless it can carry over from a flattened .jpg file. The elements I have created for this particular layout were new and all designed on this MAC w/ CS5.  I did use an old .jpg image that had a guassian blur effect on it but new elements were affected.

    This issue has happened to me in several scenarios, not just one particular.  So, I am kinda thinking it is a larger problem that deals with data conversion on a larger scale.

    Also, what is the difference between File / Open and File / Place.  I read on another forum about this and am starting to use that command to see if the quality of image maintains.  Keep in mind that my file was not blurred out.  It happened during the changes to my document/image.  I did not have to use File / Place in CS3.

    This is not the complete history.  I have since maxed out history option so I can post future issues here.  Here's my screenshot - nothing major happening - just basic steps.  This file was new and the elements had been designed over the past two months of 2012.

    It was a very visible change and it seemed like every time I took a 2nd look, something else needed to be changed.

    The center swirl was re-opened to replace the blurred out swirl on top of the photo frame.  Hope you can see this.

    mattkoyak
    Participating Frequently
    February 10, 2012

    Welcome everyone new to (what's become) the Support Group for gaussian blur corrupting Photoshop files.  My name is Matt and I'm a recovering gaussian-aholic. The only solution we've found to this problem has been to go back through the previous posts, paying special attention to the steps other designers executed to cause it, then training your staff to adjust their workflow - avoiding those steps.  There is no fix.  May the Force be with you.  Always.

    Participant
    February 10, 2012

    Totally. Same here.

    Not only corrupts the layer but the ENTIRE FILE is lost.

    I'm not using Gaussian at all now. Which leaves me in a super high disadvantage. I almost always have the need to use gaussian.

    Come on Adobe, we pay thousands for the software and an issue like this can't just be left to wonder...

    Participating Frequently
    February 10, 2012

    FYI - to all the forum newcomers, Adobe's Chris Cox and Jeanne Rubbo have been working with us for a long time now trying to get this figured out. The trouble on their end apprently is that nobody can reproduce this on command to show them, and they cannot reproduce the bug at all. So until they can reproduce it they cannot resolve it.

    If you can get it to happen on command, we are all one step closer to the solution. Just get in contact with Jeanne via her email: jrubbo@adobe.com and if you can reproduce on command she can do a screen share session with you to make some progress.

    Participating Frequently
    February 10, 2012

    Joel - just seen your response, I will email Jeanne with all the info I have.

    Participating Frequently
    January 25, 2012

    Hi, I had this issue for around 6 months and intermittently lost heaps of work.

    Touch wood I have solved it, kind of. I've had no trouble for 3 months now and all I did was buy and install OSX 10.7 and buy the upgrade to CS5.5 which includes photoshop 5.1. I am using exactly the same mac ( pro 2009/2x2.26 quad core/16gb ram/NVIDIA geforce gt 120) with same hardware set up and same graphics tablet, external drives etc - software has been the only change I have made. Was expensive and took a while but has saved me a lot of time and money in the long term. Hopefully this might help sopme of you with the same problem and adobe work out what is going wrong with photoshop 5.

    Participant
    January 25, 2012

    Be advised: Before anyone goes and buys software upgrades thinking it will solve the problem, I am running Mac OSX 10.7 and Ps 5.1 (vers 12.1), the latest versions of both, and still randomly experiening this bug.

    c.pfaffenbichler
    Community Expert
    Community Expert
    January 25, 2012

    As Pierre has pointed it out again today and out of curiosity:

    Has anyone of the people experiencing the issue fairly reliably been able to set up a remote session with Jeanne Rubbo?

    PECourtejoie
    Community Expert
    Community Expert
    January 25, 2012

    To all users affected: please see posts 38, 49, 51 by Jeanne Rubbo and reply.

    What could make your machine different than most unaffected users:

    Is the installed memory third party?

    Absolutely no other software runs when the crash happens?

    Participant
    January 25, 2012

      Model Name:          MacBook Pro

      Model Identifier:          MacBookPro8,3

      Processor Name:          Intel Core i7

      Processor Speed:          2.3 GHz

      Number of Processors:          1

      Total Number of Cores:          4

      L2 Cache (per Core):          256 KB

      L3 Cache:          8 MB

      Memory:          8 GB

      Boot ROM Version:          MBP81.0047.B24

      SMC Version (system):          1.70f5

      Serial Number (system):          I'll supply privately if needed

      Hardware UUID:           I'll supply privately if needed

      Sudden Motion Sensor:

      State:          Enabled

    No Third Party PS Plug-ins. No third party memory. Time Machine is always running. I do usually have various apps launched when using PS. I use a Wacom tablet.

    When I experience this, there are always layer masks involved on the file when I'm using the gaussian blur.

    Participant
    January 21, 2012

    Just got the same bug. Didn't even get to apply the Gaussian Blur. Saw the corruption happening while I was in the effect preview, hit cancel but it still messed up my image. Interestingly, it only effected the layer beneath the one I was attempting to apply the blur to. 14 MB RGB file contained 10 layers, 1 layer group, 2 layer masks, 1 adjustment layer, various blending modes throughout. Kind of an average file - which is troubling because it makes me think it can happen at any time.

    Like everyone else here, I need to be able to use these editing tools with complete confidence in their reliability. Please help, Adobe. Livelihoods depend on it!!!

    Thanks,

    Anthony

    System:

    10.7.2

    iMac 2.7 GHz Intel Core i5

    4GB 1333 MHz DDR3

    AMD Radeon HD 6770M

    Photoshop 12.1 x64

    Participant
    January 21, 2012

    Disregard what I said above about it only effecting one layer. Upon reopening the file, corruption has occured throughout.

    Work lost.

    Very unhappy.

    Participating Frequently
    January 23, 2012

    Happened again today, minor file corruption, but massive desktop corruption.

    Here's what it looks like (before rebooting): http://imgur.com/a/4NPJK

    Good times.