Skip navigation

Gaussian Blur in Photoshop CS5 Corrupting files

Nov 11, 2010 1:37 PM

  Latest reply: kicker1975, Sep 23, 2012 11:34 PM
Replies 1 2 3 4 5 Previous Next
  • Currently Being Moderated
    Oct 21, 2011 9:00 AM   in reply to Jeanne Rubbo

    Hi Jeanne.

     

    I am still having this issue and whilst I understand you cannot reproduce it, it is hard to send any details as the problem doesn't crash photoshop and so there's no crash report to send. I have emailed you a screenshot of my file which has just corrupted and is now un-useable. If you have made any progress on this problem please let us all know as I think we are all loosing a lot of hours reworking files that have corrupted.

     

    Thanks

     

    Neal

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 21, 2011 11:05 AM   in reply to Nam_uk

    The details needed are: what steps can reproduce this? What other things are installed with Photoshop that might cause corruption (third party plugins, utilities, etc.).

    We need all the information we can get that will help us reproduce the problem.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 21, 2011 1:51 PM   in reply to Chris Cox

    As with everyone else in this discussion I can't actively reproduce the problem. It seems to occur when a file has smart or 3d objects in it but corrupts when a blur filter is used on any layer in the document - but this doesn't happen every time and so I can't reproduce the corruption on demand. Once it has happened to a file I'm working on any file I open before closing photoshop os also corrupted in the same way.

     

    This time round I had linotype's font explorer running which has a photoshop plugin active but when I initially had the problem I tried working without the program running and it still occurred so decided that wasn't effecting anything. The only other plugin I have added to photoshop is the ICOformat.plugin for saving windows icon image files - which I have used for a long time before the problem began. I have tried resetting the PRAM and I have done an extened hardware test so it is also not a hardware problem.

     

    I would be more than happy for you to remotely look into my system. Would it be possible to do it on a non-timed basis so I could email you when it next happens and you can look at it then to see what the document looks like and how it is set up when the problem occurs. Would that be more useful?

     

    Thanks

     

    Neal

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 25, 2011 12:42 PM   in reply to Nam_uk

    Hi Neal,

     

    I've contacted you via e-mail, but just to (publicly) answer your question about any progress -- no, unfortunately, there are not any new leads on this. Hopefully we can set up a Connect session at some point in the future when you run into this again.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 7, 2011 8:34 AM   in reply to Jeanne Rubbo

    We're experienicing this problem on two of our retouching stations running CS5 Photoshop.

     

    Has anyone seen this problem in CS5.5? We were planning on waiting until CS6 came out to upgrade, but if this would stop the file corruption, I could probably swing for it for our six retouching Macs.

     

    Thanks.

     

    -- Jon

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 7, 2011 9:18 AM   in reply to moriabane58

    Inasmuch as Adobe and many others have been unable to reproduce the problem, I don't see how anyone can assure you that CS5.5 won't have the same issue.

     

     

    ____________

    Wo Tai Lao Le

    我太老了            (no connection to Adobe.)

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 21, 2011 4:33 PM   in reply to lclark00

    I have been having the same problem!

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 29, 2011 1:19 PM   in reply to lclark00

    Hi I am having an issue with corrupted files as well, but the cause of the problem is probably unrelated since the distortion is a little more dramatic. This is a screen shot of a .psd document....it should be an image of a building and landscape with about 10 layers (or somthing close to that). My problem didn't occur as i was working on the document, but rather after i had saved it and shut my computer down. when i turned my computer back on after a couple of days 3 of my most recent .psd documets had done the same thing.

     

    I am running Mac OS X 10.7.2

    2.3 GHz intel core i5

    4 GB 1333 MHz DDR3

     

    please help!

    Screen Shot 2011-11-29 at 9.07.41 AM.png

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 29, 2011 10:55 PM   in reply to Hana@MGD

    That looks more like disk corruption, and doesn't seem to be related to this topic.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 30, 2011 6:18 AM   in reply to lclark00

    Just to add to this thread, we updated two of our retouchers to CS5.5 Photoshop about three weeks ago and so far we haven't had the filter corruption issue re-occur. I'll let it run thru the end of the year and if we still haven't seen a reoccurance, we'll update the rest of the department.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 9, 2011 9:09 AM   in reply to lclark00

    I have also been encountering the problem from time-to-time since installing CS5 EXTENDED on a brand new machine. I have a MacBook Pro, with the i7 core. I usually have PS contiunually running for days at a time. No third-party software except for wacom tablet. The corruption is completely random and frustrating. Same kind of situation, using gaussian blur, and then photoshop starts drawing blocks on my files. Sometimes it's on the actual layers themselves, and sometimes just in my layer masks. Cannot undo or revert file. Just completely corrupts it with blocks of information removed. I haven't submitted a crash report since it doesn't actually "crash" my computer, just destroys the file.

     

    Attached is an image. I had just applied gaussian blur on a new layer to create a drop shadow. The corruption attacked a different layer,  and cut a hole through the photo layer (It's not a white fill), You can see my drop shadow lingering through the corruption block.

     

    Please feel free to contact me with any additional questions, and please let me know if you come out with a patch. Due to budgetory constraints, sure when we will upgrade to 5.5 since we just bought 5 in March. I will try and post more images when this happens. Hope you can figure this out!

     

    corruption_sample.jpg

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 21, 2011 9:03 AM   in reply to lclark00

    I've been having this issue since we got CS5 at work, it's doing the same thing that everyone is describing, randomly after doing a gaussian blur  layers get corrupted. After the first few times it happened we replaced all the RAM in my machine and but it still randomly happens.

     

    Model Name:Mac Pro
      Model Identifier:MacPro3,1
      Processor Name:Quad-Core Intel Xeon
      Processor Speed:2.8 GHz
      Number Of Processors:2
      Total Number Of Cores:8
      L2 Cache (per processor):12 MB
      Memory:12 GB
      Bus Speed:1.6 GHz
      Boot ROM Version:MP31.006C.B05
      SMC Version (system):1.25f4

     

    System Version:Mac OS X 10.5.8 (9L31a)

     

    No third party plugins. CS5 v12.0.4 x64.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2012 8:11 PM   in reply to lclark00

    Hi Everyone

     

    I also noticed that MANY MANY MANY of my files were beginning to look fuzzy.  At first I thought perhaps it was me resaving to often {PC system w/ Intuos 4} and now Mac.  Then I noticed while working on a few files LIVE that a clear image went a bit blurry all of a sudden.  Thankfully, I figured out that the system was making the command on it's own because when I selected "Undo" for something totally unrelated to Gaussian Blur and had not used Gaussian blur, the command "Undo Guassian" popped up.  Then, the lightbulb went off.  It is the system doing the command on its own for some reason.

     

    The other day, I worked on a vintage image graphic I had downloaded from another source.  Had worked on it in a prior session as well.  I looked over at my screen and where a few pixels had softly been removed from my edits, magic wand tool selection edits, {which was fine, I wanted the layer below to kind of show through}.  The pixels turned SQUARE!?  I have also had to close out docs without saving when I notice funky things going on. 

     

    There is a "pixel bender" file that I have noticed on the program.  Is this related to gaussian blur?  Is this a valid PS .exe?

     

    I have lots of history typically when working with my images.  Perhaps I could provide a copy to Adobe to see if technical support could figure this out.

     

    This problem has affected several documents, including logos!   So, I am thinking it is happening upon reopening files.  And as I recall, this was ALSO occuring on my old PC.  I thought I was saving incorrectly, see above.  I have a Mac now.

     

    I have a new Mac and do use an Intuos 4 Pen and Tablet.  But I am *NOT* clicking down on guassian blur.

     

    No Third Party Plugins.

     

    Typically, I have Bridge running in the background 90% of time.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 11, 2012 7:55 AM   in reply to lclark00

    HI!

     

    I have a really big problem. I work in advertising and I need to retouch a lot.

     

    When I use the guassian blur, my file becomes corrupted and I loose all my work done. A lot of strange objects and lines appear...

     

    My Mac info:

     

    Adobe Photoshop Extended 12.0 x64

     

    3,06 GHz Intel Core 2 Duo

     

    4 GB 1067 MHz DDR3

     

    ATI Radeon HD 4670 256 MB

     

    Mac OS X Lion 10.7.2 (11C74)

     

    Can anybody help me?

     

    Thanks a lot!

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 18, 2012 3:07 PM   in reply to Tontcho

    Tontcho, I hear you loud and clear.  I'm also a professional retoucher, and i've recently lost at least 40 hours of work over a few months to this (or a similar) issue.  I do have a Wacom, but when this happens, i'm not using it.

     

    It's not just gaussian blurring that does it for me though (though it does); for me, it's way worse layers with masks, or groups of layers with masks that really get things tweaked out.

     

    I've done all the usual things (prefs, etc), as well as replaced all the RAM, replaced the GPU, disabled OpenGL, reinstalled the entire CS5 Suite, and still, corruption.

     

    I've gotten into the habit of saving extremely often, but there's been more than once that i've saved while zoomed in without noticing corruption, and therefore killed large and complex (1-2gb, 50+ layers) files.

     

    Anything, literally ANYTHING will help.

     

    Thanks,

    Erik

     

    System:

    10.6.8

    2.66GHz Quad Xeon

    16GB 1066MHz DDR3

    12.0.4 x64

    NVIDIA GeForce GT120

     
    |
    Mark as:
  • PECourtejoie
    4,746 posts
    Jan 11, 2006
    Currently Being Moderated
    Jan 19, 2012 5:53 AM   in reply to lclark00

    Pixel bender is ok, it is an Adobe technology: http://labs.adobe.com/technologies/pixelbenderplugin/

     

    I'm just an user, but I am wondering:

    Most of the users affected seem to be working in a large environment/corporate/offices.

    Most seem to be usingMac Pros.

    Usually, the files are quite large.

    Is there anything peculiar about them? Smart Objects, Advanced blending, any common denominator?

    I am wondering if they run special software (anti-virus, corporate firewall, back-up solutions) if they work locally, or if the files are located on a server, if there is anything peculiar compared to a regular computer.

    Is time machine activated, on an external or internal disk? Are they all using a wacom tablet?

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 21, 2012 1:40 PM   in reply to lclark00

    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

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 21, 2012 1:54 PM   in reply to ARubolotta

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

     

    Work lost.

     

    Very unhappy.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 23, 2012 9:17 AM   in reply to ARubolotta

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 23, 2012 11:51 AM   in reply to flat1ine

    That shows a video card driver problem (and probably MacOS 10.7), not a Photoshop document corruption problem.

    Corruption of the Photoshop document would not affect the rest of the system - just that single document in Photoshop.

     
    |
    Mark as:
  • Noel Carboni
    20,990 posts
    Dec 23, 2006
    Currently Being Moderated
    Jan 23, 2012 1:20 PM   in reply to Chris Cox

    I sure am glad that on the Windows side we can get our own new display drivers directly from the manufacturer.

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 24, 2012 8:43 AM   in reply to Chris Cox

    Well, yesterday's error might not've been the right thing, but sadly, today's is ... http://imgur.com/a/oezON

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 24, 2012 12:28 PM   in reply to flat1ine

    Aaaaaand again: http://imgur.com/a/t6wI9

     

    I'm losing work like crazy here, saving often (and to different files) as things can corrupt at any time.  There's GOT to be a fix for this.

     

    I use Photoshop for about 80-90% of all the work that I do, I simply can't afford this kind of error so constantly.

     

    -Erik

     
    |
    Mark as:
  • Noel Carboni
    20,990 posts
    Dec 23, 2006
    Currently Being Moderated
    Jan 24, 2012 2:50 PM   in reply to flat1ine

    Is it possible that everyone's seeing this kind of corruption as often as you are?  I'd think there'd be a heck of an uproar here on the forum (not that a thread with 122 posts in it is chopped liver, mind you)...

     

    Have you run any diagnostics on your system?  Is it a machine that uses ECC RAM?  If not, you could be taking undetected RAM errors, and if that happens all bets are off.

     

    I think I read above that you've seen the problem with OpenGL disabled...  Specifically, did you close and restart Photoshop after having disabled OpenGL Drawing and before testing?  That would be essential for the test to be conclusive.  Might even be a good idea to reboot just to make sure there's no latent corruption in the display driver.

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 24, 2012 11:08 PM   in reply to Noel Carboni

    Just to chime in, I've had this problem occasionally. But perhaps of interest not on my work Mac Pro but on my home iMmac (thus only light use and no network).

     
    |
    Mark as:
  • PECourtejoie
    4,746 posts
    Jan 11, 2006
    Currently Being Moderated
    Jan 25, 2012 1:32 AM   in reply to lclark00

    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?

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 25, 2012 1:43 AM   in reply to lclark00

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 25, 2012 6:29 AM   in reply to PECourtejoie

      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.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 25, 2012 7:37 AM   in reply to Nam_uk

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 25, 2012 7:44 AM   in reply to ARubolotta

    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?

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 25, 2012 8:46 AM   in reply to c.pfaffenbichler

    For anyone experiencing problems, please e-mail me the info I asked for earlier in this thread. If you've already e-mailed me recently and I haven't responded, I will get back to you.

     

    I am still open to setting up Connect sessions. Again, please contact me if you are able to reproduce this problem regularly. I may not be as available in the short term, but I am still determined to get to the bottom of this.

     

    Some things to try in the meantime:

    -Restarting Photoshop occasionally. If you notice that this problem only happens when you've had Photoshop open for a number of hours (which seems to be the case for most people), then this might help.

    -Some people have reported success after a fresh installation of the OS and Photoshop. I can't guarantee this as a solution, but it might be worth a try if you are able/willing to do it.

    -Some people have reported success after replacing memory. Again, other people have not been successful with this. I'm not sure what the difference is between the machines and the replacement memory in these cases, but as in the previous option, if it's something you are willing/able to do, it might be worth a shot.

     

    As for the one person in the thread who is running into corruption frequently and seeing issues with desktop corruption as well, I agree with Chris that this looks like a hardware or driver issue.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 10, 2012 8:41 AM   in reply to Jeanne Rubbo

    Right, I'm getting this problem as well. If I apply a Gaussian blur it corrupts my image.

     

    I've just lost my third image - this really isn't good enough. My whole CS5.5 upgrade experience (Indesign as well) has been unhappy. This is the worst Adobe upgrade I've had.

     

    Is there a fix yet?

     
    |
    Mark as:
  • Noel Carboni
    20,990 posts
    Dec 23, 2006
    Currently Being Moderated
    Feb 10, 2012 8:45 AM   in reply to jeremyhopes

    Jeremy, Mac or PC?

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 10, 2012 8:56 AM   in reply to Noel Carboni

    Sorry, should have posted more info. (I'm just cross with this whole upgrade - I seem to find problems everywhere at the moment). Anyway - deep breath ...

     

    Mac Pro. 2 x 2.8 GHz Quad Xeon, 14gb ram.

     

    Seems to happen when machine has been under some heavy'ish memory loads.

     

    Initially you think it's just a display issue (that's what it looks like) - so you zoom in or out only to find most of the layers in the image have corrupted.

     

    Back in the old days (early 90's) you used to have to shut down every hour or so to clear memory. Don't tell me we're having to go back to that!

     
    |
    Mark as:
  • Noel Carboni
    20,990 posts
    Dec 23, 2006
    Currently Being Moderated
    Feb 10, 2012 9:02 AM   in reply to jeremyhopes

    I'm a PC user, and haven't seen it, but I'm interested in being whatever help I can be...  Out of curiosity, if you use the History and go back some steps, can you reach an uncorrupted version of the image?

     

    Sounds like a wild pointer issue, but I wonder why it's not seen in PCs.  Most of the same code must go into the build of Photoshop for both platforms.  Maybe it's an uninitialized pointer that happens to have an innocuous value on a PC, and a damaging value on a Mac.

     

    Can you reproduce it reliably, or is it just random?

     

    I might suggest trying to run Photoshop without OpenGL enabled and seeing if it changes the occurrence of the problem.  If it does, it's possible the Mac's OpenGL display driver implementation needs an update - and such updates only come through Apple..

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 10, 2012 9:19 AM   in reply to Noel Carboni

    Just managed to get it happen again.

     

    Apply Gaussian blur - layer it's on corrupts. Command z'ing doesn't help. Choosing revert to saved then corrupts the whole image.

     

    Closed image without saving - reopened it - looked fine.

     

    Display started to play up again - nothing serious but a section of blur wouldn't revert on a cmd z so thought I'd quite and re-open.

     

    Re-open and AGH! the image is completely corrupt. (see below).

     

    corrupt_image.jpg

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 10, 2012 9:25 AM   in reply to lclark00

    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...

     
    |
    Mark as:
  • Noel Carboni
    20,990 posts
    Dec 23, 2006
    Currently Being Moderated
    Feb 10, 2012 9:27 AM   in reply to jeremyhopes

    If you've got an image that it's easy to reproduce the problem on Adobe would very likely be interested in having a copy.  Look up-thread for the solitations for more information.

     

    Another thing to experiment with in pursuit of a workaround, since I see that the image appears corrupted in tiles...  Go into Edit - Preferences - Performance and try changing some of the settings over at the upper-right, for example Cache Levels and Tile Size.  This is just a shot in the dark, but I've been known to hit things occasionally... 

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 10, 2012 9:30 AM   in reply to rciavatta

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 10, 2012 9:39 AM   in reply to Noel Carboni

    Hi Noel - I'll email them in a bit, but it's a really simple file. And the issue is not just connected with that one file.

     

    The common factors through this thread seem to be Mac Pro's, heavy memory load, possible display issues and then playing with the blur. I'm surprised it's so hard to reproduce.

     

    I'm almost certainly going to switch back to CS4. I need to get some work done.

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points