I have encountered the same issue in our shop as well, this must be an issue with PS. I am going to monitor this fourm and see what you PS gurus come up with. I will post any information you need to assist in the correction of this problem. Thanks for the help.
We are continuing to work on this, and still need information from people who are experiencing this problem. The more people who can provide this information, the better. I'll repost a list of the information we need:
-Your system info (Help > System Info)
-List of applications you have running when the problem occurs.
-Specific information on when the problem occurs (for example, one user was seeing the problem as soon as the Gaussian Blur dialog popped up).
-Screenshot(s) of your Activity Monitor right after you run into the problem
-Sample process of Photoshop (In Activity Monitor, click on the Photoshop item in the list, then click on Sample Process at the top of the window)
-Screenshot of your History panel (~30 steps or so) right after you run into the problem
Please e-mail this information directly to me at jrubbo AT adobe DOT com.
We still want to do Connect sessions with people who can easily reproduce this problem, so please e-mail me if you are interested.
Having these same exact issues. Running Gaussian Blur in Photoshop CS5 repeatedly corrupts files. Photoshop generates these harsh blocky shapes on all layers in files, and also deletes blocky shapes in layers. Been running CS5 for five months now and have not experienced anything like this before. It's incredibly bizarre and counterproductive. Emailing system specs to Adobe now in hopes that Adobe can generate a patch for this soon.
We've never been able to reproduce the problem, and only a few people seem to have seen the problem.
We have no idea why it's happening. (and you should read the rest of the topic to see what's been discussed)
Im a designer working in packaging design studio and a few people have reported this problem. Specifically 2 people out of the 9 running CS5 have had this same issue so clearly this is a random event as we've running CS5 for several months and it is only these 2 machines that it has happened to.
I know you've mentioned that you need data and Im sorry to say I cant supply at this time, I will however try supplying it to yourselves sometime next week.
Clearly we work with documents with mulitple layers, masks and filters on a regular basis so I hope that you manage to resolve this soon. I cant imagine losing an entire graphic route as it would be a disaster, luckily up until this point it has just been a few hours work.
I'll be watching this thread to see if there are any developments.
Thanks to everyone who has posted in this thread and sent me e-mails with the requested information. Like Chris said, we still haven't been able to track this one down. It is very much on our radar, though.
For those of you who haven't sent me your information yet, I posted a list of items earlier in this thread. Please send me as much of the information as you can -- hopefully this will help us figure out what is going on.
Also, a couple of other questions that I don't think have been asked yet:
-Is there a specific point when this problem started popping up? For example, after you installed new hardware, a Photoshop update, an OS update, another application, etc.?
-Has anyone happened to make this problem go away after replacing any hardware? Usually this type of problem is related to bad memory. I'm not sure that's the case here, but I would be interested to know the experiences of anyone who has tried this.
I started getting the issue after I upgraded to CS5 from CS4. It was only a matter of a week or two. And there were definintely no hardware changes, and nothing software-wise that was Photoshop related (ie - plugins, etc).
As far as the issue going away - well I can say I haven't experienced it since before I talked with you and Chris, and the only thing I've done since then is report the issue! :-) But seriously, no, I haven't changed my hardware at all since then.
Thanks for the update. I'm glad that you haven't run into the problem again, even though that makes it tougher for us to debug.
For those of you still having the problem, could you send me another file? This time I'd like to take a look at your Mac system profile. Just open up your System Profiler app (Applications > Utilities > System Profiler). Go to File > Save As and save out a copy of your system profile, then send it to me at jrubbo AT adobe DOT com.
Well I clearly spoke too soon!!! Haha, always happens that way, too.
So I just got a crazy funky freaky error again, and here's the screenshot: http://cl.ly/54TU
Only, it didn't happen on any command, just on opening the document.
I'll send you the profile doc. :-)
We are still trying to track down this issue. For those of you encountering the error, had Photoshop been running for a while when the error occurred? If so, about how long would you say Photoshop had been running at the time? I'm trying to see if the session length might be related somehow.
Sometimes yes, sometimes no. I can recreate it on any image with multiple layers with masks that were created with a brush. The problems start when you step backward a blur applied to a non smart layer in the history.
The company I sys admin at has had two computers/artists run into this issue.
Both MacPros. but from different years a 1,1MacPro and a 4,1MacPro.
Both running on 10.6.7 of Snow Leopard.
The 4,1 had the issue after an artist used Gaussian Blur. The issue was more subtle than most the screen shots posted in this thread but upon save and reopen there was enough layer data loss/corruption to call that version of the file toast. Had the artist reopen a copy of the file before corruption- retrace exact steps and was unable to reproduce. This artist has not had the issue re-appear since. There were no recent changes to his system before the issue appeared and no changes after the issue occurred.
I would say his Photoshop CS5 12.0.2 had been running for about 2-3 hours when the issue occurred. Total system RAM about 7GB used of 12GB.
I will email his System Info to the email specified earlier in this thread.
The 1,1 machine didn't have the issue very apparent during editing but the artist noticed after saving the file that things didn't look right. These files also used Gaussian Blur. Unfortunately I do not have as many details from this artist at the moment but am trying to get what I can.
this artist had probably been using Photoshop CS5 for about 6-7 hours to the point the corruption happened. We had to grab an earlier version of the files from a backup so this artist could re-do their changes.
The last report of the issue was yesterday. This is a pretty severe issues so they would have gone through our IT at this devision of the company which includes myself and one other Sys. Admin. Of the many artist we have we've only had these two reports so far but I anticipate the reports to grow at this rate.
I will email the system info from PS CS5 from the 4,1 Mac Pro artist and then later 1,1MacPro artist after I obtain the additional details from their station.
i just want to inform you that this problems happend to 2 of my clients....
Nothing helped for now.
If you need anything to fix this problem . let me know.
I can send some files to you.. Thank you.
The current version is 12.0.4. Please install the update.
At the time this issue occurred it happened on two different MacPros running two different versions of CS5 v.12
A MacPro1,1 running PS CS5 v12.0.4
A MacPro4,1 running PS CS5 v12.0.2
Since the Latest isn't always the greatest we don't usually update every machine to the latest version. This way if there's an un-workaroundable issue in the latest we have at least a few machines on the previous version before any latest bugs have been introduced. As this isn't a bug that's specific to 12.0.2 and is occurring in the latest released build 12.0.4 we will hold off on updating our reserved 12.0.2 machines. We don't want to get ourselves stuck in an unknown 12.0.4 specific bug in a crunch period by having every machine on the latest.
At this point we haven't had the issue occur since I put in my first post on this issue. Jeanne has received both the Mac Profiler & CS5 Sys. Profile for both machines. If we find any reproducible steps or new leads we will definitely share.
I had two files open, each with multiple layers. This corruption error occured on both files... the one I was working on and the one in the background. I believe I used the motion blur filter. This problem reminds me of a trojan horse problem in the late 1990s. Then it was a matter of files just disappearing or having blue lines run through the images.
we have 20 Macs with OS X 10.6.8 and CS5.
On two Macs we have this issue. The other machines work fine.
The 2 Mac Pros are from different generations.
The problem occurs randomly.
Thanks in advance...
Sorry, no new info yet.
Even with all of the information I've been sent by various people with this issue, I have not been able to reproduce it on any of my Macs. So far, I have also not been able to see this problem occur during Connect sessions I've had with different people. At this point I would still like to set up Connect sessions with people who can get this to happen consistently. I'm working on a script or action that will trigger the bug for those of you who have encountered it -- hopefully this will increase the chances of me getting to see it happen to someone in real time.
So again, anyone who is interested in setting up a Connect session, please contact me at jrubbo AT adobe DOT com.
I think it is possible on two customer sites to reproduce this problem.
I will contact my customers if it is ok for them and if they really can
reproduce this issue.
If i get an positive response I will directly contact you!
Thank you for all.
Chris and other Adobe Engineering folks:
I may not be saying anything you don't already know, but...
One thing I used to teach my software engineers to do when they had a particularly sticky problem that couldn't be reproduced was to go do a thorough code inspection of the parts most likely involved in the issue (in your case the Gaussian Blur code). It's surprising how some things jump out just by reading the code with an eye toward discovering a particular problem...
We are facing the same problem on one machine in our agency. It´s a MacPro 2x2,66 GHZ XEON, 6 GB RAM, running on OSX 10.5.8 and the PS-Version is 12.0.4. It mostly happens with larger PSD-files with many layers. The Problem happens randomly - once the Gaussian blur has corrupted the file there is no way back. The only workaround we found is to save to a new file periodically not to risk much work.
There are no third-party filters or extensions running in Photoshop, the system is also clear of non-supported extensions. It makes no difference if fonts are used or not. However - our font management is done by Linotype FontExplorer.
We hope this problem is benn taken seriously by adobe, since many people are facing this strange effect.
It also would be helpful if someone know a similar filter like the Gaussian Blur (eventually third-party)?!
I am a freelance designer and I am also having this problem. Not only on my mac at home but also at client sites on different machines. It always seems to happen when the Guassian blur is used in conjunction with a smart layer but it doesn't always occur in every file. Once it has happened there is no way back and the file is lost. I am loosing many hours of work having to re-do things over and over again hoping that the problem won't happen this time round or doing things a longer way round to give myself the best possible chance of having a useable file. I have spoken to other freelancers who also have this issue. I really hope it can be sorted out soon as it is having a real effect on productivity.
the gaussian blur problems makes me also mad - since 1 week it corrupts files immediatly!
By now I researched in my enviroment and found to other people/macs with the same problem.
We found out the we all installed a driver for a wacom tablett...
What about you other guys here? Did you also?