Participating Frequently

Answered

Why does Photoshop CS4 keep crashing?! (Mac OS)

Forum|Forum|16 years ago
April 15, 2009
21 replies
47094 views

I use Photoshop often, daily even. I upgraded to CS4 at the beginning of this year and have a CONSTANT and very IRRITATING problem. It keeps crashing, for no apparent reason. It will crash during all kinds of "tasks". Saving, opening an image from RAW, using the liquify tool, using the clone tool, running an action and any number of others tasks cause a crash in Photoshop CS4.

I work relatively fast, as I use Photoshop on a daily basis. This is how it will happen...

I'll be working on an image and I "command S" to save. There will be a slight delay of about 2-4 seconds and then Photoshop will crash and I will get a pop-up screen to submit a crash report. I have submitted literally hundreds, if not thousands of these. Then, Photoshop sits idle for a few minutes as if it is locked up, unable to "Relaunch". So, I then usually have to "Force Quit" Photoshop, yet, it will not immediatly quit. It takes another couple of minutes to do so before I am able to begin working again. This process happens, on average, a couple of times per hour, if not more.

Luckily, I have "trained" myself to save after almost ever thing I do. But, I inevitable loose something as it happens just after a "task" or during a "save". (It happens during a save frequently.) Plus, I'm loosing valuable time waiting on it to Relaunch, and figuring out where I'm at on the image all over again.

Needless to say, I'm beyond frustrated, to say the least.

There is something else that doesn't make sense. My business partner, who also has a new IMac (not the VERY newest model that just came out but the one just prior to that...It was purchased in December 08 as well) and also runs CS4 does not have this crashing problem! At all! Not once.

Here's the difference in our systems...He purchased the 24" model, while I purchased the 20". And, this is where I actually think the problem may lie...I am running dual monitors, while he does not.

I've tried to trouble-shoot this problem, since he does not have the problem, while I do. I did "About this Mac" on both our machines to see if there were any obvious differences, besides running dual monitors. What I found under HARDWARD were only two minor differences. His processor speed is 2.8 while mine is 2.66 GHz. and the SMC Version of his machine is 1.3f1, while mine is 1.29f1. There were no differences in the GRAPHICS/DISPLAYS section either, beyond my having a second display.

Both his and my graphics/displays are as follows:

ATI Radeon HD 2600 Pro:

Chipset Model:    ATI Radeon HD 2600 Pro
Type:    Display
Bus:    PCIe
PCIe Lane Width:    x16
VRAM (Total):    256 MB
Vendor:    ATI (0x1002)
Device ID:    0x9583
Revision ID:    0x0000
ROM Revision:    113-B2250L-259
EFI Driver Version:    01.00.259
Displays:
iMac:
Resolution:    1280 x 800
Depth:    32-bit Color
Core Image:    Hardware Accelerated
Main Display:    Yes
Mirror:    Off
Online:    Yes
Quartz Extreme:    Supported
Built-In:    Yes

Below is the information regarding my second display.

LaCie 324:
Resolution:    1920 x 1200 @ 60 Hz
Depth:    32-bit Color
Core Image:    Hardware Accelerated

Main Display:    Yes
Mirror:    Off
Online:    Yes
Quartz Extreme:    Supported
Rotation:    Supported
Television:    Yes

As you can see, my second display is a Lacie 324. It is rather new, I purchased it in November or December 08 as well as my IMac. I have the Lacie set as my main display.

When I have Googled this Photoshop CS4 crash problem, I have come across some mention of the GPU Settings and Enable OpenGL Drawing. I have to admit, I really don't understand this. Should OpenGL Drawing be on or off??? I turned OpenGL Drawing off some time ago because I had a problem with calibrating my Lacie monitor. My monitor was showing images skewed toward red, while my prints were coming out with less red. I Googled this problem (at the time I didn't think this was related to the crashing issue) and someone said they were having trouble calibrating their monitor as well and managed to "fix" that by turning "Enable OpenGL Drawing" off. I did that and it did indeed fix the problem with getting my Lacie monitor calibrated. FYI, my business partner also turned off the Enable OpenGL Drawing feature and...again...he has NOT had the problem with Photoshop CS4 crashing. So, since he is not having the problem and I am, I would assume the "Enable OpenGL Drawing" issue that is mentioned on this site, is not the crashing problem, though I could be wrong.

So, I go back to having a second monitor as being the most-likely candidate for causing the Photoshop crashes. I am wondering if the Lacie display is "drawing" the graphics at the speed that differs, or is incompatable, with Photoshop CS4??? This is just a guess from someone who is not all that technically savy. But, again, I'm not sure. I have also looked on the Lacie website for any updates for the Lacie 324. There are none, as far as I can tell.

I am curious if others with and without dual monitors are having these crashes. If so, have you found any resolution? I'm desperate for help so if anyone can shed any light on this issue, it would be most appreciated.

Below, I will put some specs about my machine, in case that is helpful.

Hardware Overview:

Model Name:    iMac
Model Identifier:    iMac8,1
Processor Name:    Intel Core 2 Duo
Processor Speed:    2.66 GHz
Number Of Processors:    1
Total Number Of Cores:    2
L2 Cache:    6 MB
Memory:    4 GB
Bus Speed:    1.07 GHz
Boot ROM Version:    IM81.00C1.B00
SMC Version:    1.29f1

I have the 11.0.1 version of Photoshop CS4.

PLEASE help if you can. Thanks so much!

DGJ [email address deleted by host]

This topic has been closed for replies.

Correct answer adobesuxisalreadytaken

Sorry to post in the wrong forum! I just wanted to quickly vindicate Adobe, though, after my rather jaded previous post. I just downloaded the update from Adobe Automatic Updates and Photoshop hasn't crashed since. Don't know if that will help you Mac folks or not, but I thought I'd just let you know. Good luck!

E

earlvarona

Participant

Sorry to hear that but I got the same problem (but not as often as yours). What pisses me off is it takes the files I saved with it when it crashes (so that work that I saved but still open will no longer recover). I don't know what's wrong with it but I'm considering upgrading to CS5.5 soon if this keeps happening. The best of luck to you!

Chris Cox

Legend

If you've installed all the updates (to 12.0.4) and it's still crashing often, chances are you're looking at a third party plugin bug or an OS bug.

stewart tower

Known Participant

I'm not helping; just ranting.

I find CS4 in general to be a buggy piece of garbage. I spend the bulk of time in ID and PS with constant issues from both. I've long since given up looking for solutions but have found some relief that I'm not alone. PS crashes on every single quit; ID constantly loses all my pallets and also likes to crash when quitting (although no where near as often as PS).

I used to send friendly reports to Adobe about it but in the last 4 months or so I've taken to harshly rebuking them for this abomination; so much so that I no longer get a report dialog when PS crashes. Has Adobe seen the light and disabled my reporting mechanism?

We purchased a multi site version of CS4 with varying degrees of success amongst us, even though we all installed from the same disks. Go figure!

While I don't expect perfection from any new upgrade, but do expect possible anomalies; I've never seen such a horrible piece of software outside of MS Office. CS5 came out fairly soon after CS4 so I took that as a sign that CS4 had some serious issues. We don't have CS5 yet but I'm hopeful that it's just one big patch.

Chris Cox

Legend

PS crashes on every single quit;

Which third party plugins did you install just before it started doing that?

Though it's also possible you have a Brother printer/scanner (but a lot less common).

Has Adobe seen the light and disabled my reporting mechanism?

No, you had to disable the crash reporter. Adobe can't do that. If you go into your preferences folder and delete the adobe crash reporter plist, that'll reset it.

And you do know that while we fix bugs and report problems to third party manufacturers, there's no way we could respond to each and every crash report -- right?

CS5 came out fairly soon after CS

Historically, each version ships 18 to 24 months after the last. CS5 was no exception.

stewart tower

Known Participant

I've installed no third party plugins; CS4 has been acting this way right off the disk.

I have not consciously disabled my reporting mechanism so let's just add that to the bug list. But thank you for pointing out the plist tip.

While admittedly frustrated, I'm still sane enough to know that Adobe does not reply to every crash report. My guess is that crash reports are scanned by software and not people. If Adobe does employ people to process crash reports they must have some serious overtime issues going on right now.

I've been using Adobe software from the time it came on floppy disks with printed manuals and have been through enough hardware and software upgrades in 16 years to justifiably state that CS4 has been my worst software experience yet. The only one that's topped is so far has been Publisher. I'm actually worried that Adobe might have gotten a bit too comfortable like Quark did (you all remember Quark, right?).

D

DGJ193Author

Participating Frequently

Well this is DGJ again...the original poster of this topic. I've been out of town a bit but have been back for the last week and wanted to post an update on my "crashing" problem. I'm hoping I've figured it out. Some of my crashing very well could be caused by the things Chris Cox has mentioned. But, I've greatly reduced my crashes by simply unpluggin my external hard drives!

I can't believe it! What clued me in was when my biz partner bought a new 1 TB external hard drive and when he began using it, he began having crashes, which he had not had before. So, he ended up returning that hard, a G Tech 1 TB, and replacing it with a Sea Gate 1 TB. FYI, on the G Tech external hard drive...it was purchased at the Apple store and was suppose to be "apple compatible" so I tried it srtaight out of the box but that caused crashes. Then we reformatted it for a Mac but that made no difference. It was attached directly to the computer and daisy-chained as well. It made no difference.

So, I returned that G Tech 1 TB external hard drive and exchanged it for another, thinking I just got a "bad" one. But, the second one did the same thing, caused crashes. (As a reminder, this was on my biz partners machine.) So, I checked my external hard drives and realized I had Lacie and a 500 GB G Tech external hard drive. So, I simply disconnected all the hard drives and have been working for a week without any attached.

And....

NO CRASHES!

I wanted to test this out a bit before posting here again. I wanted to be certain I had troubleshooted the problem before "assuming" I had a fix. So, you have seen my crash reports and some may have been due to this external hard drive issue or may be due to the issue Chris Cox noted or both. But, my crashes have ceased.

Hopefully, if any others have had this problem, you can see if disconnecting your external hard drives helps you. As a reminder, initially, I thought it might be due to having dual monitors. I guess that was not the case.

I'm just happy to have my issues corrected! It's been maddening and I can't believe I didn't think to unplug those external hard drives sooner! It was stupid! But, you live and learn!

I will post if I have additional crashes.

I just wanted to thank everyone for all the help. I really appreciate it.

-

-_JM_-

Known Participant

Jesper-

Thanks for the info.

What percentage of the reported PS crashes are due to "_SetDstBits32BGRA"?

A common problem that I have experienced and others too, is that when trying to force Quit PS after the app freezes, PS won't force quit. What is causing PS to not force quit? Would all of the crashes that result in the same force quit problem have a similar origin, or is the force quit problem independent of the reason for the initial freezing of the app?

thanks

j

D

DGJ193Author

Participating Frequently

Hey JM,

I realize your question is for someone else but wanted to respond because I have had this "Photoshop won't force quit" problem as well. I can't say whether I've had a crash report mention this, " _SetDstBits32BGRA ". The crash report that I listed here of mine did not have this.

What I will say is that I did, and still do have, a Photoshop force quite problem. I don't believe this has anything to do with the G Tech issue I had. But, when I was having crashes, Photoshop would be frozen, unable to fully quit either with going through "file > quit" or through force quite. It would take a few minutes for it to actually "quit".

Then the other day, there was a storm and I wanted to just quickly quit everything and shut down (this was not due to a Photoshop crash). I began to force quite everything I had opened. However, the only one I had issue with was Photoshop CS4. I thought it was odd since I had just associated the "unable to force quite" problem with my crashing problem, which I now believe had to do with my G Tech external hard drive. But, I guess it was not.

It is very irritating as you have to "wait it out" until it finally does actually quit.

So, I am still having this issue but as of late, it was not associated with a crash.

(FYI...I just had a few programs opened and decided to "test it" and see if I could force quit Photoshop. And it didn't quit. It's frozen and unusable until it actually quits and is restarted. For the record, I timed it and it took just over 2 minutes to quit. But, I will say it's taken longer in the past.)

Dedra

Jesper Storm Bache

Adobe Employee

FYI: The crash that involves _SetDstBits32BGRA is an occasional crash in the OSX text edit field that can happen when you drag something (such as a panel) over the text edit field.

We have been able to provide a reproducible test case to Apple.

If you plan on contacting Apple regarding this issue, then you could refer to Apple bug (radar): 6913072 Crash in Carbon text edit fields when dragging

Chris Cox

Legend

Ah, good to know.

I didn't realize that you'd narrowed it down that far.

(Jesper is an Adobe engineer)

D

detailed_joy16B8

Inspiring

so Photoshop is the only program to use these APIs? Would it have anything to do with the new cross-platform UI in CS4?

Chris Cox

Legend

No, Photoshop is not the only program using those APIs, nor the only program seeing crashes due to them.

We're not sure what is causing them - we can't know until Apple finds the cause of the crash in their code.

D

detailed_joy16B8

Inspiring

Please download the attached file to view this post

1773971.doc

Chris Cox

Legend

"GetDstBits32BGRA"

That's part of the QuickDraw crashers that Apple introduced in MacOS 10.5. Also reported, also waiting on Apple to fix them.

J

J MW

Participant

Hi Chris,

Sorry, I didnt mean the actual code. It's just that it's much easier if we know what the problems are. The OP is already getting fingers pointed in both directions. If the crash reports that everyone is sending in point to a problem with the OS then it would be best if we knew what not to do in the meanwhile that its "hopefully" being fixed.

Does "text crash" point to font issues?

I had misc crashes last month and went through some extensive cleaning and organizing, and this seemed to help.

regards

j

Chris Cox

Legend

No, the "text crash" means that we use a text entry control somewhere in the UI, and the Apple code for that crashes for unknown reasons. It seems worst when opening SFW or ACR, but crashes just about anywhere at any time -- only in MacOS 10.5.x. MacOS 10.4.x hasn't seen that crash at all.

Same things for the QuickDraw crash - it crashes at seemingly random times when the application draws something. Kind of hard to avoid.

If there was something simple you could do to avoid it, we would have already said or done something (like we have for font, TWAIN, and driver crashes).

J

J MW

Participant

Hi Chris

Much appreciated.

We buy hardware and software, send in crash reports and it tends to be a one way conversation as we wait for the occasional bug fix and unfortunately get tangled up in trying to repaiir problems that sometimes (as in this case) are not within our ability to fix.

In a way, we are all partnered in business, the Adobe products are critical to our everyday work so I appreciate you taking the time to explain and to know that this is an active process.

regards

j

D

DGJ193Author

Participating Frequently

Chris,

One more thing...

The crash reports you are referring to...are they mine or the other guys???

Chris Cox

Legend

DGJ193 - that's why I quoted the important lines from each report I was responding to.

D

DGJ193Author

Participating Frequently

What can I say...

First, thanks so much Chris for looking into this. Funny that you posted just as I was having my third crash of the day. (I've only been at the computer for about 2 hours!) I have started a folder with my crash reports in there so I can see if I can tell what the trigger is.

This one was caused when I select the liquify tool. But, it's very random. Anything...I mean ANYTHING can cause a crash. I have the 11.5.7 update so I was thinking this might help. Honestly, right now I have to say it's worse!

So, Chris, how can these Apple bugs be affecting me and not my biz partner? We have basically the same machine. It's weird. He has had no crashes (except when he had a G Tech 1 TB hard drive attached). I will say I'm pretty fast and he's not as much so. I have no idea if the speed at which I work is an issue but...who knows.

Also, I will update by saying I disconnected the G Tech 1 TB hard drive from my computer (thinking it may be the issue since my biz partner had problems with his.) I do, however, have two others connected. So, I'm going to try disconnecting them. I think both are 500 GB hard drives. One is a G Tech and the other is a Lacie. Disconnecting the one hard drive has not made any difference. But, I'll do the others and post again if this helps.

So, who should I call to scream at? Apple? I've got some choice words I'd really like to say to someone as this has taken my usual quick productivity down to a turtle's pace. Just force quitting Photoshop after the crash can take upwards of 5 minutes! I save after every task but still loose things. And I work so fast it's hard to regain my thoughts as to where I was in my retouch project! So I have to re-orient myself. CRAZY!!!

I NEED to yell at someone. My business partner is tired of hearing me complain & curse!

Thanks for all the help.

(Below is the "top" of my most recent crash report.)

Dedra

Chris Cox

Legend

Apple hasn't given us the details of their text related crashes. (or most of their crashes for that matter)

My guess is that the crash depends on some history and configuration -- what operations were done before, how much RAM is available, what plugins are loaded, etc. That changes what values are in memory, and when a bug happens it frequently reads a wrong location from memory (or one that wasn't initialized) and may crash depending on the exact value read. It could even come down to what fonts are installed, or what web sites you recently browsed -- we just don't know.

Some of the Objective-C crashes, I have absolutely no idea about. We've identified a lot of fragile parts of the Objective-C runtime and loader code and reported those to Apple.

In that respect we're in the same boat you are: we see problems, we gather data and report them, then wait.

D

DGJ193Author

Participating Frequently

Okay. Update. I finally broke down, thanks to Chris, and called Apple. It went, of course, just as I expected. They were very nice, Especially since I had to pay $185 ish for the Apple Care. I went a little nuts over having to spend $185 for what is a problem with Apple, not me. But, as I knew they would, they said they wouldn't know if it was an Apple problem and most times it's not Apple, its third party programs. He said third party programs are suppose to write code to work with Apple, not the other way around. So, it's basically that, "You did it!", "No! It was you!", finger-pointing nightmare that I knew it would be.

You know what...I don't give a rats A who did it. I just want it fixed.

So, after I went through $185, a 45 minute phone call and much frustration, the "cleaning" didn't work. I feel certain the reinstall won't either.

Nonetheless, for those out there who want or need to do a through cleaning of you Mac. Let me save you $185 and tell you how (per Apple Support).

First, quit all programs, leaving the Finder opened.

Click the Mac HD > Library

Find the "Caches" folder and click it opened.

Click a file and select all and send it to the trash.

Now, click the folder with your name (with the little house)...your home folder.

Click the "library" folder there and find the "Cache" folder.

Do the same thing. Select all and move to trash.

Now, empty trash.

Now, do a shut down.

Once it's shut down hold the shift key down while hitting the power button to turn the computer back on.

Keep the shift key in until the spinning circle, circles 3 times, then let go of the shift key.

It will take about 5 minutes for the computer to start up from here.

Now, you'll do disk utility.

So, go to your Mac HD > Applications and select Disk Utility.

On the left, you'll see the very top item that says something like... 465.8 GB WDC WD5000. (Yours will be different.)

Just below that, kind of tabbed over you will see "Macintosh HD". Click that.

Then, click Repair Disk Permissions.

This will take about 5-15 minutes perhaps more depending.

Now, you are going to do another Shut Down.

This time, you are going to hit the power button "ON" and quickly & immediatly hold in the following 4 keys: P, R, Command, Option.

Keep these 4 keys held down together until your computer chimes 2 times.

Now, you're done.

So, if you think..."I need to clean my computer" because it is running slow and sluggish, do this. Don't call Apple. Don't pay $185.

My next step is to uninstall and reinstall Photoshop CS4. I will keep you up to date as to whether this helps.

I'll say this. I disconnected all my hard drives and worked for about 2 hours after my Apple Cleaning without a crash. I plugged one in to get a file off and forgot to disconnect it and had a crash about 15 minutes after it was attached. Probably just a coincidence. But, it's worth noting since my biz partner had crashes with a bad external hard drive. I will also say that typically after I restart, I get about 2 hours of work before the first crash. Then they come ofter. So, I'm going to try disconnecting the external hard drive and see if I get a crash. If I don't, that would be very curious.

I'll keep you up to date.

Also, I should mention I don't think these crashes are related to a font issue. I realize bad fonts can cause these problems. However, I didn't mess with my fonts until about 2 weeks ago, when I finally added all the fonts from my old machine. The crashes have been occurring since December. I have Suitcase Fusion 2 and Font Doctor so I ran Font Doctor and got rid of the bad fonts.

Chris, you mention crashes can happen because of recent websites I just browsed. Is there something I can do after browsing and prior to working that could help this, like deleting history, emptying Cache or anything like that???

Thanks,

Dedra

D

detailed_joy16B8

Inspiring

Please download the attached file to view this post

1773951.doc

D

detailed_joy16B8

Inspiring

Please download the attached file to view this post

1773952.doc

Chris Cox

Legend

Application Specific Information:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSCFType drain]: unrecognized selector sent to instance 0x199584f0'

Thread 0 Crashed:
0   com.apple.CoreFoundation          0x97200f54 ___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___ + 4
1   libobjc.A.dylib                   0x921e4e3b objc_exception_throw + 40
2   com.apple.CoreFoundation          0x97187a53 CFRunLoopRunSpecific + 4355
3   com.apple.CoreFoundation          0x97187c78 CFRunLoopRunInMode + 88
4   com.apple.HIToolbox               0x94abf28c RunCurrentEventLoopInMode + 283
5   com.apple.HIToolbox               0x94b727ac GetNextEventMatchingMask + 100
6   com.apple.HIToolbox               0x94b7260e WNEInternal + 151
7   com.apple.HIToolbox               0x94b7256d WaitNextEvent + 54

That's an Apple bug of some kind. Their Objective-C runtime encountered a problem. It could be due to a plugin that used Objective-C and then unloaded the UI, which is a known defect in Apple's Objective-C runtime code (but a big problem that may not get a fix soon).

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000c765a8f3
Crashed Thread: 0

Thread 0 Crashed:
0   libobjc.A.dylib                   0x921f0688 objc_msgSend + 24
1   com.apple.HIToolbox               0x94b2d57c IdleTimerVector + 59
2   com.apple.CoreFoundation          0x97187ac5 CFRunLoopRunSpecific + 4469
3   com.apple.CoreFoundation          0x97187c78 CFRunLoopRunInMode + 88
4   com.apple.HIToolbox               0x94abf28c RunCurrentEventLoopInMode + 283
5   com.apple.HIToolbox               0x94b72907 GetNextEventMatchingMask + 447
6   com.apple.HIToolbox               0x94b7260e WNEInternal + 151
7   com.apple.HIToolbox               0x94b7256d WaitNextEvent + 54

Well inside Apple's code, Objective-C runtime, could be the same sort of problem as above.

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000094a18a8
Crashed Thread: 0

Thread 0 Crashed:
0   com.apple.QD                      0x92c943cd _SetDstBits32BGRA + 8
1   com.apple.QD                      0x92cb64f0 DevFrameRect + 795
2   com.apple.QD                      0x92c7b89d StdRectWithPort + 267
3   com.apple.QD                      0x92c7b77b CallRect + 53
4   com.apple.QD                      0x92cb61d3 FrameRect + 43

QuickDraw bug, reported to Apple and was SUPPOSED to be fixed in 10.5.7 (grumble).

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x00000000ffdf4060

Crashed Thread: 0

Thread 0 Crashed:

0 com.apple.HIToolbox 0x9357d4d8 RemoveEventHandler + 48

1 com.apple.HIToolbox 0x9369e122 CCarbonEventHandler::InitCarbonEventHandler(TXNCarbonEventInfo*) + 344

2 com.apple.HIToolbox 0x9369df8e CTextension::StartCarbonEventHandler(OpaqueTXNObject*, TXNCarbonEventInfo*) + 112

3 com.apple.HIToolbox 0x935e52e2 OpaqueTXNObject::InstallCarbonEventHandler(OpaqueWindowPtr*, OpaqueWindowPtr*) + 384

4 com.apple.HIToolbox 0x93691858 OpaqueTXNObject::AttachObjectToWindowRef(OpaqueWindowPtr*, unsigned char) + 388

5 com.apple.HIToolbox 0x936d2430 TXNAttachObjectToWindowRef + 66

Hmm, another text related crash inside Apple's text code. Could be related to the previously mentioned TSNDelete crasher. I really hoped they fixed all of those in 10.5.7.

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x00000000fb1afa1c

Crashed Thread:

Thread 0 Crashed:

0 ??? 0x548df005 0 + 1418588165

1 libSystem.B.dylib 0x90071fd1 fork + 17

2 com.vertustech.FluidMaskPlugin 0x2003c2e2 0x20037000 + 21218

3 com.vertustech.FluidMaskPlugin 0x2003c3bc 0x20037000 + 21436

4 com.vertustech.FluidMaskPlugin 0x2003d37f PluginMain + 111

This is a bug in your Vertus FluidMask plugin. Contact the plugin vendor.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded