Crash acr 6.1

when i use spotting brush in acr i often need to turn off visibility of spotting "circles." I press "v" and circles are cleared. when i press"v" a second time, to restore circles, acr immediately crashes with loss of image and all editing. CS5 itself does not crash.
using trial cs5 extd, imac i7, 8GB, mac os 10.6.3

Crashing described in initial post was the fault of conflict between photoshop and a utility app called TYPINATOR.
Closed Typinator and problem with acr ceased.
Should note that there is a new version of Typinator which I have not tried but this may fix the conflict.
again, there is no problem with camera raw now.

Similar Messages

Straighten tool repeatedly crashing ACR

I havn't seen this issue reported anywhere else, but I can't get it to go away.
I am using CS4 with everything updated. I shoot using a 5dmkii and canon 40d. I never had this problem in CS3
I'll load up some raw files (doesn't seem to be affected by how many images I load at once) and go to use the straigten tool. Sometimes I'm good for a 20+ straigtening adjustments before it crashes, but then ususally once it crashes if I load them up again it will crash within one or two uses of the straightining tool.
reseting tool preferences in photoshop and resting preferences in bridge will help it work for awhile, but inevitbly it will crash again while using this tool.
No other tools have any problems, and if I don't use the straighten tool my computer can load 400+ 5dmkii raw images make adjustments and crops with no trouble.
Anybody have any thoughts?

I am also having this problem. Here is the info of what I'm using:
OS: Windows 7 Ultimate (Final Release - with all updates installed)
HP Compaq 6710b
Processor: Intel Core2Duo 2.1ghz
Memory: 4GB Ram
Adobe Photoshop Version: 11.0.1 (11.0.1x20090218 [20090218.r.523 2009/02/18:02:00:00 cutoff; r branch]) X64
Bridge CS4 3.0.0.464
Camera RAW 5.4
Camera - Canon 40D shooting L JPG + RAW
The staighten tool seems to be the cause of my Camera RAW (or Bridge?) crashing. Like the previous poster mentioned, it is sporadic, but once it happens, it seems to stick each time I try. It also doesn't seem to matter how many RAW files are open. I tried going through the first few steps in an Adobe Bridge CS4 troubleshooting article, which included clearing the preference and cache, etc. Also, it was mentioned that I should try without having other programs open. I tried this as well, and it didn't help.
Any new insight into this issue?

ACR 4.5 Did Not Fix Photoshop Bug Crashing

I posted this in June
Bug: Multiple Files Open ACR Crashes Photoshop...
Buko, "Bug: Multiple Files Open ACR Crashes Photoshop..." #1, 10 Jun 2008 2:57 pm
I just went back to my normal workflow with ACR 4.5 (after leaving it because of the problem) and got the new Photoshop crash report after working on about six files.
The workflow: .nef> Bridge> ACR> 16-bit aRGB (moving sliders Black/Mids/Exposure usually generates the crash)> resizing to 500 pixels and Save AS .psd (leaving the .psd files open seems to be the switch that causes the problem)
I can repeat the problem consistently:
Drag folder containing D200/D300 .nef files into Bridge, and going to work as described...if I don't leave my .psd files open I don't have a problem, if I leave them open as I work, I usually get the crash after 5-10 files.
I emailed crash reports to CC back in June,

UPDATE: I pulled the 12gb of macramdirect ram and tested with only 2gb OEM Apple ram (to rule out the 3rd-party ram per Jeff Schewe's theory I duplicated the crash within 15 minutes. My money remains on the BUG theory, but will swap out the OEM ram and continue...if that doesn't work I will install ACR 4.6 and retest... Today's CRASH REPORT: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd"> <crashreport version="1.1" crVersion="2.5.0.02272007" applicationName="Photoshop" applicationVersion="10.0.1" build="10.0.1 (10.0.1x20071012 [20071012.r.1644 2007/10/12:09:30:00 cutoff; r branch]), ©1990-2007 Adobe Systems Incorporated"> <time year="2008" month="10" day="2" hour="15" minute="50" second="29" /> <user guid="5F46434A-15D5-4A63-A652-31682CE59DD0" /> <system platform="macintosh" osversion="10.5.5" applicationlanguage="en" userlanguage="en" oslanguage="en_US" ram="2048MB" machine="i386" model="MacPro3,1" cpuCount="8" cpuFreq="2800MHz" busFreq="1600MHz" /> <crash exception="Unmapped Memory Exception" instruction="c683068b"> <backtrace crashedThread="0"> <thread index="0"> <stackStatement index="0" address="0xffff07c2" symbolname="unknown"/> <stackStatement index="1" address="0x9327efd9" symbolname="__ZN18CTextensionIOSuite17SearchIOSuiteTypeEmP11TDataHeaderh"/> <stackStatement index="2" address="0x9327ef17" symbolname="__ZN18CTextensionIOSuite16FreeSuiteObjectsEm"/> <stackStatement index="3" address="0x9327eee6" symbolname="__ZN18CTextensionIOSuite16FreeSuiteObjectsEv"/> <stackStatement index="4" address="0x9328c9af" symbolname="__ZN18CTextensionIOSuite4FreeEv"/> <stackStatement index="5" address="0x93248cd7" symbolname="__ZN22CTextensionEditCommand4FreeEv"/> <stackStatement index="6" address="0x9328c7ed" symbolname="__ZN15OpaqueTXNObject4FreeEv"/> <stackStatement index="7" address="0x9328c71e" symbolname="_TXNDeleteObject"/> <stackStatement index="8" address="0x2fcc4a6f" symbolname="_EntryFM"/> <stackStatement index="9" address="0x2fc9286e" symbolname="_EntryFM"/> <stackStatement index="10" address="0x2fc58104" symbolname="_EntryFM"/> <stackStatement index="11" address="0x2fc53c7e" symbolname="_EntryFM"/> <stackStatement index="12" address="0x2fc94c2e" symbolname="_EntryFM"/> <stackStatement index="13" address="0x2fc58104" symbolname="_EntryFM"/> <stackStatement index="14" address="0x2fc53c7e" symbolname="_EntryFM"/> <stackStatement index="15" address="0x2fc74047" symbolname="_EntryFM"/> <stackStatemen

PS keeps crashing (with large files from ACR)

Is anyone else having problems bringing large files in from Camera Raw and PS keeps crashing over and over?*

Using CR2 Raw images working in Bridge and ACR, I was trying out the Tools/Photoshop/Process Collections in Photoshop which made my machine crash the most. The folder in Bridge is 8 GB and has about 230 images, so it was gathering tons of images and making collections. It just may be my machine and OS, need to update. I have not had a chance to read link in prior message above, I will asap. I was worried about putting the beta on my machine, I will read into this some more, thank you for your reply. Love a lot of the new enhancements very excited about some of the simplest changes made.
I am on Mac OS X 10.6.8

Adobe Camera Raw ACR crashes instantly when hitting accent key

I just lost several hours of work because ACR 8 with PS CC2014 crashes every time you hit the accent key ´ which is under to the Volume up and down keys on a German keyboard.
An error message says: "The command could not be completed because of a program error." See screenshot.
Is that a known bug?
Thank you
Marco
BTW: The ACR interface looks like it's from the nineties. How long will Adobe drag this through upgrades?

MPPhoto wrote:
…I am not talking about any dialog boxes here…
…<sigh !>…
Yes you are, Marco.
The Adobe Camera RAW window is a modal dialog box. All its tabs are modal dialog boxes.
All dialog boxes MUST close when the Escape key is pressed, or a key that somehow acts somewhat like the Escape key is pressed.
You cannot get around that, Marco. Sorry if that irritates you, but that is reality.
All we do here is try to help people and offer workarounds.
If you're prone to hitting that key too often accidentally, perhaps the workaround would be for you to disable it, either by re-mapping the offending software keyboard layout, or by physically removing or otherwise disabling it in your hardware keyboard.
If the Adobe Camera Raw Team determines it is an Apple OS bug in the mapping of that key on a German keyboard, I can guarantee you that it will be quite a while before Apple fixes that.
I am now assuming you're on a Mac because of the interface shown in your screen shot.
I understand you are frustrated, and I feel for you for having lost many hours of work for a momentary gesture of inattention, but so far you have not given any details whatsoever about your setup.
BOILERPLATE TEXT:
If you give complete and detailed information about your setup and the issue at hand,
such as your platform (Mac or Win),
exact versions of your OS, of Photoshop (not just "CS6" or "CC2014", but something like CS6v.13.0.6, or CC2014 v 15.0.x) and of Bridge,
your settings in Photoshop > Preference > Performance
the type of file you were working on,
machine specs, such as total installed RAM, scratch file HDs, total available HD space, video card specs, including total VRAM installed,
what troubleshooting steps you have taken so far,
what error message(s) you receive,
if having issues opening raw files also the exact camera make and model that generated them,
if you're having printing issues, indicate the exact make and model of your printer, paper size, image dimensions in pixels (so many pixels wide by so many pixels high). if going through a RIP, specify that too.
A screen shot of your settings or of the image could be very helpful too,
etc.,
someone may be able to help you (not necessarily this poster, who is not a Windows user).
Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
http://forums.adobe.com/thread/419981?tstart=0
MORE BOILERPLATE TEXT, extracted from another FAQ:
https://forums.adobe.com/thread/375816?tstart=0
Do not be abusive or aggressive in your tone
An aggressive, demanding, accusatory or abusive sounding post will often evoke an aggressive or abusive and unhelpful reply.
Remember, you are not addressing Adobe here in the user forums. You are requesting help from volunteers users just like you who give their time free of charge. No one has any obligation to answer your questions.
Thanks!

ACR 4.6 and PSE6 Organizer still crashes

I posted this a long time ago for ACR 4.5 and I'm gonna do it again for CR 4.6. Please read below I'm still having the same problem with ACR 4.6 (BETA).
I'm experiencing the following problem when I download ACR 4.5 to be used with PSE6.
The problem is that the PSE6 Organizer crash when I try to open the Organizer Preferences. Aparently this only happens with Windows
Vista because I know of other users with XP and they are not expiriencing this.
I did try it with the original ACR 4.2 and works well.
I did try it with the previous ACR 4.4 and works well.
It only happens when you install the 4.5 and go to the Organizer's Preferences.
And stills happens with ACR 4.6.
When I contact the Adobe Customer Support they told me to wait until the new version of ACR, well I guess that nobody there analyze/investigate/test my issue.
Regards
Hector

Héctor,
I ran ACR 4.5 for a short while with Photoshop Elements under Vista Home Premium without ever seeing your problem.
Being a Mac user accustomed to the full version of Photoshop, which I still use on my Mac desktop, I was so frustrated by the limitations of Photoshop Elements I was running on the Windows Vista laptop that I asked for a refund from Adobe (and got it too). But I never had anything crash on me while running ACR 4.5 on it.

PSE6 Organizer Crash with ACR 4.5 (Vista Only?)

Hello;
I'm experiencing the following problem when I download ACR 4.5 to be used with PSE6. The problem is that the PSE6 Organizer crash when I try to open the Organizer Preferences. Aparently this only happens with Windows Vista because I know of other users with XP and they are not expiriencing this.
I did try it with the original ACR 4.2 and works well.
I did try it with the previous ACR 4.4 and works well.
It only happens when you install the 4.5 and go to the Organizer's Preferences.
Regards

Ramon,
Sorry I made a mistake, now it is Ok.
In fact as I installed the new "Camera Raw.8bi" file, I moved the old file renamed "Camera RawOld.8bi in an "old" folder created in "..\Plug-Ins\File Formats". It was not a good idea because PSE6 was always seing the old version (despite renaming and moving in an "Old" folder). Now I've renamed the old file Camera Raw.old and all is Ok.
Thanks for your help.
Yvan

CS4 ACR 5.1 Did Not Fix Crashing

I was able to duplicate the problem in CS4/ACR5.1 in my first attempt using five layers in my problem workflow.
It appears at least part of the problem is happening in Photoshop (outside of ACR).
Would it be possible to hookup with a PS engineer to see if I can generate any useful crash reports to help expedite a look into the problem?
Thanks...

>> (GB wrote): I had such funky nasty hangs in 10.5/CS3 ACR and PS blinking out I thought I had bad hardware so I got an 8-core to write off the problem...the problem followed the 8-core so I was holding out for updates
ACR 5.2 appears to have fixed the funky nasty spinning beach ball crashes in ACR 5.1 thanks to behind-the-scenes followup by Eric Chan), however it revealed another crash problem in Ps CS3 and CS4 that a Ps engineer followed up on.
Today, on my first try in a matter of 30 minutes, I was able to duplicate the Ps crash (Ps blinking out) for the CS4 Ps team via me working remote on one of their boxes using only nine of their NEF files/layers.
I mention this only to say thank you, Adobe, for listening to me (I feel vindicated in my original instinct that my hardware and installs were good).

Bug: Multiple Files Open ACR Crashes Photoshop...

I have several small files (500 pixels wide) and ACR crashes Photoshop (three times in last hour) when I make small moves with the sliders Exposure/Blacks/mids.
I don't seem to have this problem when I don't keep several open files.
I have noticed this over some time now and the key to repeating the problem is having several files open in PS and opening/adjusting d300 nef files in ACR.
This is 8-core, 14000 MB ram, 10.5/CS3extended (all updates ran)

Well I built another 100-layer 720x540 .psd file before it Crashed with the following Report keeping a max 2 files open (Bridge> .nef> ACR> Photoshop 16-bit) has greatly reduced my ability to reproduce this crash, but not eliminated the problem -- sigh... <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd"> <crashreport version="1.1" crVersion="2.5.0.02272007" applicationName="Photoshop" applicationVersion="10.0.1" build="10.0.1 (10.0.1x20071012 [20071012.r.1644 2007/10/12:09:30:00 cutoff; r branch]), ©1990-2007 Adobe Systems Incorporated"> <time year="2008" month="6" day="20" hour="19" minute="37" second="5" /> <user guid="5F46434A-15D5-4A63-A652-31682CE59DD0" /> <system platform="macintosh" osversion="10.5.3" applicationlanguage="en" userlanguage="en" oslanguage="en_US" ram="14336MB" machine="i386" model="MacPro3,1" cpuCount="8" cpuFreq="2800MHz" busFreq="1600MHz" /> <crash exception="Unmapped Memory Exception" instruction="c683068b"> <backtrace crashedThread="0"> <thread index="0"> <stackStatement index="0" address="0xffff07c2" symbolname="unknown"/> <stackStatement index="1" address="0x902f962d" symbolname="__ZN18CTextensionIOSuite17SearchIOSuiteTypeEmP11TDataHeaderh"/> <stackStatement index="2" address="0x902f956b" symbolname="__ZN18CTextensionIOSuite16FreeSuiteObjectsEm"/> <stackStatement index="3" address="0x902f953a" symbolname="__ZN18CTextensionIOSuite16FreeSuiteObjectsEv"/> <stackStatement index="4" address="0x90306ffb" symbolname="__ZN18CTextensionIOSuite4FreeEv"/> <stackStatement index="5" address="0x902c3357" symbolname="__ZN22CTextensionEditCommand4FreeEv"/> <stackStatement index="6" address="0x90306e39" symbolname="__ZN15OpaqueTXNObject4FreeEv"/> <stackStatement index="7" address="0x90306d6a" symbolname="_TXNDeleteObject"/> <stackStatement index="8" address="0x2ee213a3" symbolname="_EntryFM"/> <stackStatement index="9" address="0x2edefb52" symbolname="_EntryFM"/> <stackStatement index="10" address="0x2edb561a" symbolname="_EntryFM"/> <stackStatement index="11" address="0x2edb1be6" symbolname="_EntryFM"/> <stackStatement index="12" address="0x2edf1d06" symbolname="_EntryFM"/> <stackStatement index="13" address="0x2edb561a" symbolname="_EntryFM"/> <stackStatement index="14" address="0x2edb1be6" symbolname="_EntryFM"/> <stackStatement index="15" address="0x2edd1d13" symbolname="_EntryFM"/> <stackStatement index="16" address="0x2edb561a" symbolname="_EntryFM"/> <stackStatement index="17" address="0x2edb1be6" symbolname="_EntryFM"/> <stackStatement index="18" address="0x2edf3cf9" symbolname="_EntryFM"/> <stackStatement index="19" address="0x2edb561a" symbolname="_EntryFM"/> <stackStatement index="20" address="0x2edb1be6" symbolname="_EntryFM"/> <stackStatement index="21" address="0x2edf4fd1" symbolname="_EntryFM"/> <stackStatement index="22" address="0x2edb561a" symbolname="_EntryFM"/> <stackStatement index="23" address="0x2edb1be6" symbolname="_EntryFM"/> <stackStatement index="24" address="0x2edd1d13" symbolname="_EntryFM"/> <stackStatement index="25" address="0x2edb561a" symbolname="_EntryFM"/> <stackStatement index="26" address="0x2edb1be6" symbolname="_EntryFM"/> <stackStatement index="27" address="0x2edf3cf9" symbolname="_EntryFM"/> <stackStatement index="28" address="0x2edb561a" symbolname="_EntryFM"/> <stackStatement index="29" address="0x2edb1be6" symbolname="_EntryFM"/> <stackStatement index="30" address="0x2edf4fd1" symbolname="_EntryFM"/> <stackStatement index="31" address="0x2edb561a" symbolname="_EntryFM"/> <stackStatement index="32" address="0x2edb1be6" symbolname="_EntryFM"/> <stackStatement index="33" address="0x2edd1d13" symbolname="_EntryFM"/> <stackStatement index="34" address="0x2edb561a" symbolname="_EntryFM"/> <stackStatement index="35" address="0x2edb1be6" symbolname="_EntryFM"/> <stackStatement index="36" address="0x2edb1d6b" symbolname="_EntryFM"/> <stackStatement index="37" address="0x2ec79868" symbolname="unknown"/> <stackStatement index="38" address="0x2edb561a" symbolname="_EntryFM"/> <stackStatement index="39" address="0x2edb1be6" symbolname="_EntryFM"/> <stackStatement index="40" address="0x2edd1d13" symbolname="_EntryFM"/> <stackStatement index="41" address="0x2edb561a" symbolname="_EntryFM"/> <stackStatement index="42" address="0x2edb1be6" symbolname="_EntryFM"/> <stackStatement index="43" address="0x2edd1d13" symbolname="_EntryFM"/> <stackStatement index="44" address="0x2edb561a" symbolname="_EntryFM"/> <stackStatement index="45" address="0x2edb1be6" symbolname="_EntryFM"/> <stackStatement index="46" address="0x2edd1d13" symbolname="_EntryFM"/> <stackStatement index="47" address="0x2edb561a" symbolname="_EntryFM"/> <stackStatement index="48" address="0x2ee147b9" symbolname="_EntryFM"/> <stackStatement index="49" address="0x2ee14a01" symbolname="_EntryFM"/> <stackStatement index="50" address="0x2ecc5f80" symbolname="_EntryFM"/> <stackStatement index="51" address="0x2ee04f8a" symbolname="_EntryFM"/> <stackStatement index="52" address="0x2ee04bc7" symbolname="_EntryFM"/> <stackStatement index="53" address="0x2ee04c6c" symbolname="_EntryFM"/> <stackStatement index="54" address="0x2ee04cd3" symbolname="_EntryFM"/> <stackStatement index="55" address="0x2ecc656f" symbolname="_EntryFM"/> <stackStatement index="56" address="0x2ec8e63b" symbolname="unknown"/> <stackStatement index="57" address="0x2eca7eb3" symbolname="unknown"/> <stackStatement index="58" address="0x2ee06176" symbolname="_EntryFM"/> <stackStatement index="59" address="0x2ee099cf" symbolname="_EntryFM"/> <stackStatement index="60" address="0x2ecaea1b" symbolname="_EntryFM"/> <stackStatement index="61" address="0x0073cb5a" symbolname="unknown"/> <stackStatement index="62" address="0x00474448" symbolname="unknown"/> <stackStatement index="63" address="0x0047511a" symbolname="unknown"/> <stackStatement index="64" address="0x00474d2b" symbolname="unknown"/> <stackStatement index="65" address="0x00479187" symbolname="unknown"/> <stackStatement index="66" address="0x0050e151" symbolname="unknown"/> <stackStatement index="67" address="0x004cfeae" symbolname="unknown"/> <stackStatement index="68" address="0x0007e712" symbolname="unknown"/> <stackStatement index="69" address="0x0007eb7c" symbolname="unknown"/> <stackStatement index="70" address="0x00b50dcf" symbolname="unknown"/> <stackStatement index="71" address="0x0007e273" symbolname="unknown"/> <stackStatement index="72" address="0x00065187" symbolname="unknown"/> <stackStatement index="73" address="0x004755a9" symbolname="unknown"/> <stackStatement index="74" address="0x0006594a" symbolname="unknown"/> <stackStatement index="75" address="0x00065a6f" symbolname="unknown"/> <stackStatement index="76" address="0x000688cb" symbolname="unknown"/> <stackStatement index="77" address="0x000676c7" symbolname="unknown"/> <stackStatement index="78" address="0x000602ee" symbolname="unknown"/> <stackStatement index="79" address="0x0006045d" symbolname="unknown"/> <stackStatement index="80" address="0x00060570" symbolname="unknown"/> <stackStatement index="81" address="0x00219cd6" symbolname="unknown"/> <stackStatement index="82" address="0x00219d31" symbolname="unknown"/> <stackStatement index="83" address="0x00003272" symbolname="unknown"/> <stackStatement index="84" address="0x00003199" symbolname="unknown"/> <stackStatement index="85" address="0x00000002" symbolname="unknown"/> </thread> </backtrace> <registerSet> <register name="CS" value="0x00000017"/> <register name="DS" value="0x0

ACR 8.4RC DNG conversion can create files that crash Adobe DNG Codec 2.0

If I use the ACR 8.4 DNG converter to convert a raw file from my newly acquired Fuji X-T1, and I use the default compatibility option of ACR 7.1, the resulting DNG file causes Windows Explorer to crash whenever I navigate to the folder that contains the file.
I believe that this is happening because Adobe DNG Codec 2.0 is trying to create a thumbnail for the file, and it is not capable of dealing with DNG files that require the Camera Raw 7.1 demosaicing algorithm.
If I convert the same raw files and ask for ACR 6 compatibility, I don't have any problem navigating to the resulting folder. However, the resulting DNG files are much larger. Moreover, I understand that those files have already been demoasiced, which means that any future improvements in demosaicing algorithms will be moot.
My question, then, is whether the DNG Codec will be updated any time soon to handle files produced by the 8.4 DNG converter.

I’m on Windows 7 SP1, 64-bit version. So far as I know, I’m current on windows updates.
A sample image can be found at https://www.dropbox.com/sh/izcl857d37fmtdc/sGj2wuG3LF
Of course, it is possible that some other codec on my computer is the cause of the crash. However, I know for certain that
When I uninstall DNG Codec 2.0, I get no thumbnails for these images and no crash.
When I (re)install DNG Codec 2.0, Windows Explorer crashes the moment I navigate to the folder that contains these images.
I have found no problem with DNG files created from other manufacturers’ raw files.

ACR crashes sometimes when doing clone touch-up

This has now happened to me 4-5 times (over the last 3 months) and I'm recently motivated to post here because I lost about 30 minutes of ACR edits last night on a crash.
Occasionally when I'm editing a lot of pictures in ACR where the images involve cloning areas of the photo (I'm often trying to eliminate a stray item from the background in my soccer photos), I get a crash in ACR (hosted in Bridge). It's always while I'm using the clone/heal tool. It's not reproducible in that it works most of the time, but just crashes sometimes.
I've seen this problem in both ACR 4.1 and 4.2.
Has anyone else seen this problem?

What OS? What CPU? What ram allocation to Photoshop?

Bridge CC crashes while using arrow keys to switch images

Adobe Photoshop CC 2014 Adobe Bridge 2014 on Mac is crashing every time I press an arrow key to move through images in bridge. I can click to manually select images with no problem, but using the up/down arrow keys to move to the next image up/down brings up the spinning beach ball and immediately locks the program up, requiring a force quit.
Did the usual Mac permissions and fsck stuff to no avail. Ideas?
Dan

Thanks for moving my post to this correct forum. (I'm afraid I missed it when I originally posted.) A bit more information based on attempts to fix and on further attempts to use the program.
After launching Bridge — before I select any specific image — it initially seems to work correctly. For example, I can use menu items and select and open folders. However...
Once I drill down through folders to show raw files in the browser the problems begin. I can manually select an image by clicking on it, but the program the locks up if I do things such as attempt to navigate to another image using the up/down keyboard arrows or select anything from a menu that would perform an action on the image. (The problem happens with any image selected — not one particular image, and with images that worked fine until 48 hours ago.)
ACR still works. I can double click an image and open the raw converter, and I can doubly click a smart object image in Photoshop do go back to the raw editor and it allows me to edit.
I did the step of holding down command-option-shift at Bridge startup and selecting all three options to delete the cache and so forth. Still no joy.
I did the usual Mac disk/file system repair stuff — repairing permissions and repairing disk — to no avail.
I downloaded and reinstalled Bridge but the problem persists.
Since I have a full backup of the drive on which Bridge is installed and since this backup drive is bootable, I double clicked the copy of Bridge on the backup drive... and it opened (slowly!) but worked correctly. (Not that this means much, but my second instance on my laptop continues to run fine.)
I'm stuck, in a serious way, at this point. Thoughts?
Thanks,
Dan

Bridge CS5 won't open at all, crashes immediately

Hi you guys,
I have been using Photoshop CS5 for a number of months now, without any problems. Yesterday, just suddenly, Bridge just bombed out. And I mean it crashes completely, not even a spinning ball or a 'stop responding', it just disappears from the screen. The first time the crash generated an Apple Crash Report, as well as an Adobe one. After that, when I click on the Bridge icon, it bounces, no dot appears on the dock under the icon and after a while the icon stops bouncing and another Apple Crash Report gets generated. It does not generate an Adobe crash report because, I suspect, the program does not go far enough.
I have tried the following:
Option clicked the B Icon - straight to Apple crash report.
Open B in PS, PS works perfectly and stays operational, but B generates an Apple crash report. I also tried mini B, the dock opens with message "waiting for Bridge", and nothing further happens.
Checked permissions in my Library for the following, all well:
Caches/Adobe/Bridge CS5
Application Support/Adobe/Bridge CS5
com.adobe.bridge4.plist file
Verified and repaired permissions in DU, just in case. No luck.
Created a new user account and tried to open B - straight to Apple crash report.
Deleted the PLIST file and the items in Cashes (as suggested in another tread) - straight to Apple crash report.
I have not yet tried a reinstall. I upgraded to CS5 from CS3 and I still have it sitting on my hard drive. In a previous thread I asked what to do with CS3 and the consensus was to leave well alone. Everything worked and I did not need the disk space. In fact, Bridge CS3 still opens without a problem. If a reinstall is necessary, how do I go about it then? Do I
deregister CS3 and CS5 and uninstall and reinstall the whole lot?
deregister and uninstall and reinstall CS5 only?
don't deregister and just reinstall the whole lot without uninstalling it first?
don't deregister and just reinstall CS5 only without uninstalling it first?
And if I have to uninstall, do I have to run one or all of the cleanup utilities of Adobe?
I have also not contacted Adobe help because I have an American copy of Photoshop and live in Europe. That disqualifies me from Adobe support.
Here is my system:
iMac 5 with 2.16GHz Intel Core 2 Duo
Mac OS X 10.6.6
Adobe CS5 12.0.2
Bridge CS5 4.0.4.2
Thanks in advance!
Jay
And for you guys who can read the gibberish, here is some of the crash report:
Process:         Adobe Bridge CS5 [698]
Path:            /Applications/Adobe Bridge CS5/Adobe Bridge CS5.app/Contents/MacOS/Adobe Bridge CS5
Identifier:      com.adobe.bridge4
Version:         4.0.4.2 (4.0.4.2)
Code Type:       X86 (Native)
Parent Process: launchd [132]
Date/Time:       2011-02-12 23:07:18.163 +0100
OS Version:      Mac OS X 10.6.6 (10J567)
Report Version: 6
Interval Since Last Report:          2508 sec
Crashes Since Last Report:           1
Per-App Crashes Since Last Report:   1
Anonymous UUID:                      CFAC5A0D-23FB
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: 0x000000000000000a, 0x00000000035ef0a4
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0   AdobeCoolType                  0x035ef0a4 0x35ec000 + 12452
1   AdobeCoolType                  0x038c0c69 0x35ec000 + 2968681
2   dyld                           0x8fe0ed6d ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 235
3   dyld                           0x8fe0d31e ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int) + 246
4   dyld                           0x8fe0d2c2 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int) + 154
5   dyld                           0x8fe0d2c2 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int) + 154
6   dyld                           0x8fe0d3d1 ImageLoader::runInitializers(ImageLoader::LinkContext const&) + 61
7   dyld                           0x8fe024a9 dyld::initializeMainExecutable() + 134
8   dyld                           0x8fe07950 dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**) + 4189
9   dyld                           0x8fe018b1 dyldbootstrap::start(macho_header const*, int, char const**, long) + 779
10 dyld                           0x8fe01057 _dyld_start + 39
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x0392e78c ebx: 0x038c0c45 ecx: 0x8fe44840 edx: 0x0000ff01
edi: 0x038c1080 esi: 0x00000000 ebp: 0xbfffd688 esp: 0xbfffd66c
ss: 0x0000001f efl: 0x00010202 eip: 0x035ef0a4   cs: 0x00000017
ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
cr2: 0x035ef0a4
Binary Images:
[VERY LONG LIST WITH LOTS MORE GIBBERISH]
Model: iMac5,1, BootROM IM51.0090.B09, 2 processors, Intel Core 2 Duo, 2.16 GHz, 4 GB, SMC 1.9f4
Graphics: ATI Radeon X1600, ATY,RadeonX1600, PCIe, 128 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x87), Broadcom BCM43xx 1.0 (5.10.131.36.1)
Bluetooth: Version 2.3.8f7, 2 service, 19 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: WDC WD2500, 232,89 GB
Parallel ATA Device: MATSHITADVD-R
USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8501, 0xfd400000
USB Device: Hub, 0x050d (Belkin Corporation), 0x0237, 0xfd100000
USB Device: Extreme III USB2.0 Reader/Writer, 0x0781 (SanDisk Corporation), 0xa1a2, 0xfd110000
USB Device: Hub in Apple Pro Keyboard, 0x05ac (Apple Inc.), 0x1003, 0x5d100000
USB Device: Apple Pro Keyboard, 0x05ac (Apple Inc.), 0x020c, 0x5d130000
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8206, 0x7d100000
USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8240, 0x7d200000
FireWire Device: d2 quadra (button), LaCie, Up to 400 Mb/sec
FireWire Device: d2 Quadra (button), LaCie, Up to 400 Mb/sec
Message was edited by: JfromSA

Hi guys,
Thanks for your time and trouble. Much appreciated.
I haven't been back because my iMac went from bad to worse and in the end I've had a complete system crash. The 2007 iMac G5 I have, is notorius for screen problems. Mine went pop in 2009 after only 18 months of use and was replaced by Apple after a war of words and overwhelming evidence of similar problems for that model on the internet. During that episode the machine was shut down with the power button several times, by me, by the shop and also by the technicians who had to diagnose and repair the computer (I have often wondered why Apple does not have an equivalent of the 'Windows' button, because via that it's easy to shut down a PC blind: Windows button>U>Return . . . the OS shuts down. Not clever of a company who regards themselves as 'Quality' with a self proclaimed capital Q). I suspect my computer picked up some hardware damage with the constant hard shutdowns. I was actually waiting for the next problem, I never really trusted the machine completely. But, as time passed, I got relaxed about it and did not notice the small signs developing like Bridge (and to a lesser extent, Photoshop) actually slowing down more and more the last couple of weeks. Now, in retrospect I can say that, but it was really very subtle. I did, after the screen episode, got into a routine of backing up my system regularly.
After the Bridge problem began, I tried a re-install, a Time Machine restore and eventually started fiddling with Disk Utility, trying to fix the hard drive. To make a long story short, all I get now when I power up the machine is a white screen with a spinning disk under the Apple emblem. I do know that the internal hard drive had issues because that was reported by Disk Utility, I still do not know what the damage is because I still have to take the machine in for repairs.
In the meantime, I am working on another iMac. I have installed all my software from scratch and I'm now trying to restore my old system - my PS actions, ACR actions, all my mails and other documents and my music. The problem I now have is that I had my user account encrypted with File Vault, while backing up with Time Machine. To everyone doing that, please don't - turn File Vault off and then back up. All my carefully backed-up files are now encrypted and can only be accessed with my broken computer! I can NOT restore my system to another computer! With older versions of Mac OS X (and, probably Time Machine), it's possible to use Finder to navigate to the encrypted back-up folder, double-click it and access your data with your master password and restore it by simply dragging and dropping the files on the new computer (but under no circumstances delete or change the back-up files in any way! And applications would, most probably not drag and drop without a problem, but there I stand to be corrected). With OS X 10.6 it is not possible any more to access data via Finder in that way. I know, because I can access my data up to end 2009, the rest is there but not accessible. I have searched everywhere on the internet and as yet, have not found a solution.
The other problem with Apple, I found out, is that in normal operations, it works so well and all is so easy that I don't really read any instructions. There is no need. Everything just happens, it's actually too intuitive. Not once, while setting up File Vault or Time Machine, was I warned that it might be a problem. Now, when I poke around on the internet, there are many posts that warn against that but I did not search for them because I had no clue! I just hope, after the faulty parts on my G5 is replaced, I can get into my back-ups. I shall keep searching and trying to find a solution. If I get one, I shall post here again for those of you with similar problems. I know this is no longer a Bridge or Adobe problem, I just thought I must report back, maybe the knowledge will help someone else.
Cheers,
Jay

How do I make ACR 4.6 start saving edits to PSDs again?

When I develop an image in ACR 4.6 and save it to a psd, the psd looks like the original dng, not the processed image -- no edits are saved even though I use Save Image or Open Image. It's been working fine for years. I have the same versions of dng converter and ACR on my Macbook Pro, and it still works fine. When I did a reinstall, it worked for about one or two files, and then broke again. I'm running os 10.4.11 on G5, PS 10.0.1, ACR 4.1.0.30, Bridge 2.1.1.9, DNG Converter 6.3.0.79. One clue might be that if I try to access Bridge's Preferences, Bridge always crashes instantly. I'd be grateful for any help. Thanks.

Hi Jeff,
You're absolutely right, it should show as 4.6, and it does. My error. The initial inquiry should have read, 4.6.0.30 (and yes, that was the last version for PS 10.0.1).
However, you have helped me solve my problem. I changed the ACR Preferences to, "Apply sharpening: to all images" instead of "Apply sharpening: Preview images only". I'm not sure exactly what that means, but it must have been the default each time I reloaded 4.6. Or perhaps I changed that without remembering, preventing the developed ACR version being applied to the psd.
I have no idea why Bridge Prefs crash as soon as I select them in the menu. Camera Raw Prefs accessed from Bridge don't crash when selected. I'll try to figure that out separately.
Thanks very much for your assistance.

Can't install ACR updates in Windows 7

When I try to install downloaded updates, I get a message that the installer "... has encountered a problem. Close Adobe Bridge before continuing installation." Except that Bridge is not running, and I have no clue about why it thinks it is. Other updates have the same problem (Adobe Reader) but some have installed. Does anyone know what's happening here?
There are other issues, such as the straighten tool in ACR will not draw a line and will crash Photoshop.
Windows 7 HomePremium 64-bit and Photoshop CS4 64-bit.

Hi,
Could you post the contents of your AIR installer log? It's possible, depending on the error we received, we might also need the MSI log.
Thanks,
Chris

Crash acr 6.1

Similar Messages

Maybe you are looking for