Ok - by your response it seems to be a coincidence! What a pity! ;o)

Maybe you could help make that progress if you/your colleague can reproduce the issue and take Jeanne Rubbo up on her offers (posts 38, 51, …).

Unfortunately just like everyone else here it is a random issue that proves to be something difficult to reproduce.

We conducted some in-house training to teach our designers how to adjust their workflow to avoid this issue.  Here's what we try to avoid: create a new file, place a few smart objects on seperate layers, apply a few layer masks and apply gausen blur (without converting the layer for smart filters) to a low ranking layer in your new document.  Then, make some changes to the layer mask on the layer that has the gausen blur with the brush tool, ereaser tool, whatever and then start to step back your work using command + z. Eventually, Ps is unabl to process the "undo" and the layermask on the gausen blur freaks out corrupting your file. 

Personally, I can destroy a file 4 out of 10 times by following those steps.  The more layers with GB + layer masks applied the better, and it helps if your placed images are large  (2000px x 2000px or greater).  Does it recreate the problem 100% of the time... no.  Has it happened since we started avoding those steps... no.

same thing happens to me. About to go back to CS4.

iMac 3.1 GHz intel i5 pretty much stock. I am running a wacom tablet and the latest driver for it.

Usually happens when running a gausian blur but has also happened when running a motion blur.

also when going edit/stroke when trying to put a stroke on a selection I have to save before doing so. About 50% of the time applying a stroke like that will crash this version of photoshop.

Very disappointed in this version to say the least. It has been the buggiest version I have ever used for the particular way that I work.

Chris,

I have read the entire thread. I am running a practicly brand new iMac which is stock and have no 3rd party plugins installed other than a wacom driver. Photoshop 12.0.4  x64 and Mac OS 10.7.1

I have not submitted any crash reports when photoshop crashes when stroking a selection because I figure they fall on deaf ears. If you could tell me exactly what I need to do I will submit a crash report next time this happens.

It is a big headache when I lose a little bit of work when the stroke crash happens but a much larger issue when I lose an entire document because I applied a blur.

aw man seems I opened a can of worms that I didn't intend to. I meant nothing disrespectful about the falling on deaf ears comment. Just figured you guys are too busy to listen to a single customer so I never bothered with submitting a report.

I will definitely submit something next time it happens.

not taking anything personally but didn't want to seem like I was being disrespectful or insulting. It is all too easy for something to be taken out of context on the internet.

I hit a nerve? Try rebuiding an entire file because of a glitch that not only messed up the last half hour of work but actually corrupted the entire file to the point where it is unusable even though you didn't save the file once it corrupted.

I definitely won't be hitting any more nerves. Won't be posting here again and cerainly won't be upgrading or supporting your company in any form or fashion until I am forced to. Tired of shoddy programs. Tired of companies pointing the finger at each other over whose fault something is. Tired of getting the short end of the stick because accountants really run the show because at the end of the day it is all about profits and most definitely tired of being a real world tester so that big companies can save a penny.

There are bugs in this program that have been here since it's introduction on OS X. I have had hundreds upon hundreds of dollars worth of nerves hit over the years not to mention time lost due to rebuilding files due to data corruption in this latest build that apparently can't be reproduced. None of this even begins to approach the frustration with the house of cards named Adobe Illustrator. I have lost all faith in your company and once astounding products and only use them because of there is nothing else available due to monopolization.

I was trying to be nice. Trying to chime in that I too am having a issue. Even went as far as to clarify that I wasn't trying to be a jerk but still got told how I upset you. That is all good because I have been upset with the products out of this company for some time. At least we understand each other.

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

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

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

I have been having the same problem!

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!

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.

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

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

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.