Lightroom CC Crashes when selecting 1:1 crop

Anyone else having this issue? As soon as I select a square 1:1 crop the app crashes.

I've been reading more that the GPU support does little on older Macs I'll turn it off and see what happens. thanks Scott

Similar Messages

Lightroom 5 crashes when selecting a video

finally deduced it was when I clicked a video for flagging. I removed the videos from the catalog but that defeats the purpose. I tried the ui.dll and did rename the ui.dll.old file. I unstalled and reinstalled LR5 and update to 5.3. Its working now but like I said I removed the video.
issue was when I put in the ui.dll then LR would not even open up so effectively I did not do the ui.dll because I couldnt,. I did it successfully for lr3 when I had the edit/flagging crashes without issue this is weird. thoughts?

windows 7 i7 HP system 6G RAM no recent updates etc except 5.3
It definitely is kicking out when I click to play a video or on the video grid box etc. I retried with different videos I have loaded. I have since edited a few pictures and flagged and imported and no concerns; weird that is only video. No I havent removed pref file. Isnt that under LR where the catalog is? If I delete it it will recreate itself? then I can re enter my prefs? thanks

Lightroom 5 crashes when selecting "Slideshow"

Like the title says, every time I click on "Slideshow", LR5 crashes - immediately (it does start to set up the screen for this module, but never completes). I tried LR4.4 and it works fine. I recently upgraded (about 3 weeks ago) to LR5 from 4.4, and I haven't had any significant problems otherwise.

Try removing the Preferences File/s. Look here for instructions: http://helpx.adobe.com/lightroom/kb/preference-file-locations-lightroom-41.html
If that does not help next try removing the .lrdata file from your catalog folder and rebuilding previews.

Lightroom 4 crashes when trying to open the slideshow module. I spent over three hours with both Adobe and Apple tech support and we know it is a permission issue but have not been able to get it solved. It started with the last upgrade to 10.8

Lightroom 4 crashes when trying to open the slideshow module. I spent over three hours with both Adobe and Apple tech support and we know it is a permission issue but have not been able to get it solved. It started with the last upgrade to 10.8

Back up all data.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
Step 1
If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
Triple-click the following line to select it. Copy the selected text to the Clipboard (command-C):
{ sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -Rh $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2 (optional)
The first step should give you usable permissions in your home folder. This step will restore special attributes set by OS X on some user folders to protect them from unintended deletion or renaming. You can skip this step if you don't consider that protection to be necessary.
Boot into Recovery by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open.
In the Terminal window, type this:
resetpassword
That's one word, all lower case, with no spaces. Then press return. A Reset Password window will open. You’re not going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.

Photoshop CS6 crashes when using burn tool, crop tool, and dodge tool?

Just recently upgraded from Photoshop CS5.5 64bit to Photoshop CS6 64 bit. Crashes when using burn tool, crop tool, or dodge tool? Thanks for your help!

Turn off OpenGL in the prefs and update your graphics driver before re-enabling it.
Mylenium

Photoshop CS6 crashes when selecting tools

Hi, I'm having the same problem as a few other members (Photoshop CS6 occasionally crashes when selecting tools) and have updated the driver on my HD5770 card to the latest version (8.961.0.0) as this is the recommended fix. Unfortunately this hasn't fixed the problem.
Here is the error report from the most recent crash.
This is very irritating as I inevitably lose some of my work when the application crashes.
What else do you suggest as a fix?
Steve

I installed 12.3 and restarted my computer. This did not solve the problem.
I've reinstalled Photoshop twice as well with no developments.
Then, I found this thread: http://forums.adobe.com/message/4289204
My card (Radeon X 1300 / X 1550) is not listed in the "Tested video cards for Photoshop CS6" section.
If I go to Edit->Preferences->Performance, and mouse-over the "Graphics Processor Settings" section, it says "Photoshop detected an error in your display driver. Update or reinstall the driver and check Use Graphics Processor to retry".
Is there any way around this?

InDesign CC crashes when selecting text

Hello folks!
I have a serious issue here on my Windows 7 64bit notebook:
InDesign CC (and also CS6 before) keep crashing when selecting text.
I was still on CS6 when this failure appeared first. The strange thing is, it happens not always. When InDesign is opened new it will not crash instantly (most times). After some selecting random text a few times InDesign will crash with the well known "InDesign doesn't work anymore" message. There seems no pattern while selecting text (like special characters, certain fonts, whatever).
Tried to use CC – no luck! still crashing.
After some research in the forum I read, that this is very rare issue only occuring if there are more than 1 Windows accounts with both InDesign running. Indeed I made new account shortly before the first time this happened.
But sadly even after I completely wiped the second account, all my InDesigns (CS5, CS6, CC), all prefs, and also all fonts (as recommend in a thread with people havong trouble with just the type-tool itself) and all registry thingies the problem remains. Why?
Please help, it really kills the productivity.
Thanks in advance for everything!

Well, wonky extension seems like a good idea, but can be withdrawed because I haven't installed one.
The font issue is also equally probable. As already mentioned: The interesting aspect here is, that both InDesign CS6 and CC will crash. It happened the first time when Windows decided to blue screen and f*** up my account (I wasn't able to log in anymore, I had to made a new one). I once read in another thread that there is a problem occuring when having multiple Windows accounts with InDesign running. Re-installing InDesign didn't help. Font problem after all?
I have installed at the moment:
MainType
NexusFont
Typograf
and some small others, like: dp4 Font Viewer or FontViewOk

JVM crashes when selecting non-default printer in ReportViewer in NATIVE dialog.

On ReportViewer frame i have the print button active. If i click the print button (Native dialog) and select a printer other than default printer, the JVM crashes. Any idea how to fix it?
Thanks

I wanted to provide little history of what I am trying to achieve. Currently, I have the following code:
PrinterJob printJob = PrinterJob.getPrinterJob();
        if (printJob.printDialog()) {
            String printerName = printJob.getPrintService().getName();
            String printJobName = printJob.getJobName();
            PrintReportOptions printOptions = redirectPrinter(printerName, printJobName);
            sendReportOutputAndClose(reportClientDoc, printOptions);
I want to capture the number of copies user selects from the dialog. When I do printJob.getCopies(), it always returns 1. Not sure how to get that # of copies user selected. I also wanted to the dialog to be in Native mode because I don't want to give access to modify Margins and other page properties which are part of COMMON dialog mode. If I create the dialog printJobAttribute.setDialog(JobAttributes.DialogType.NATIVE); then VM crashes when selecting a non-default printer but I am able to get the number of copies. The key is I need to use NATIVE dialog and get the number of copies. One option is to display in COMMON dialog mode and then hide the "Page Setup" and "Appearance" tabs. Can this be done ? I am new to Java and Crystal so any suggestions would help.

Elements 13 crashes when selecting Print

Elements13 crashes when selecting Print from the File menu.
Rebuilding the Preferences file will bring the Print menus back, but only temporarily.
No error message, Windows advises the program must be shut down.
Win 7, 16GB RAM, Elements 6 on the same computer works fine.

Hi ,
You are going through File menu > Print or File menu > Order Prints .
Meanwhile go to Edit menu > Preferences >> Adobe partner services .
Click "Refresh Button"
Click "Reset Account"
and "Clear On-line Serves data" also.

JVM crashes when selecting a CLOB in a OracleCallableStatement

Hi all:
We have a lot of places in our codebase where we "batch" a no. of
selects using the OracleCallableStatement for better performance (i.e.
save multiple roundtrips to the db). Recently we upgraded to Oracle
8.1.7 and converted the LONG column in one of our tables to CLOB. Once
we did that, every place in the system where we use a "batch" select
(using refcursor) the JVM crashes (no stack trace, just the infamous Dr.
Watson on NT and SIGBUS SEGV on Solaris)
We are running wl510 sp10 , driver is weblogic oci (oci817_8).
Here is a sample code
cstmt = (OracleCallableStatement)con.prepareCall(
"BEGIN \n"
+ " OPEN ? FOR SELECT A, B, C FROM TAB1 where ..;\n"
+ " OPEN ? FOR SELECT X, Y, Z FROM TAB2 where ..;\n"
+ " END;");
cstmt.registerOutParameter(1, Types.OTHER);
cstmt.registerOutParameter(2, Types.OTHER);
cstmt.execute();
rs = cstmt.getResultSet(1);
Is there an update or patch for the driver which resolves this issue?
thanks much,
mohan

I wanted to provide little history of what I am trying to achieve. Currently, I have the following code:
PrinterJob printJob = PrinterJob.getPrinterJob();
        if (printJob.printDialog()) {
            String printerName = printJob.getPrintService().getName();
            String printJobName = printJob.getJobName();
            PrintReportOptions printOptions = redirectPrinter(printerName, printJobName);
            sendReportOutputAndClose(reportClientDoc, printOptions);
I want to capture the number of copies user selects from the dialog. When I do printJob.getCopies(), it always returns 1. Not sure how to get that # of copies user selected. I also wanted to the dialog to be in Native mode because I don't want to give access to modify Margins and other page properties which are part of COMMON dialog mode. If I create the dialog printJobAttribute.setDialog(JobAttributes.DialogType.NATIVE); then VM crashes when selecting a non-default printer but I am able to get the number of copies. The key is I need to use NATIVE dialog and get the number of copies. One option is to display in COMMON dialog mode and then hide the "Page Setup" and "Appearance" tabs. Can this be done ? I am new to Java and Crystal so any suggestions would help.

Lightroom 5.5 Crashes when selecting multiple photos in Library mode

Had this issue when I originally upgraded to Lightroom 5 last year.
Working through a large batch of photos, renaming and weeding, Lightroom is crashing every 10 minutes or so.
Is there a patch to fix this like there was with the original problem last year?
Running Windows 7 64 Bit.

When monitoring GDI Objects in Task Manager I can see the value climbing by approx 70 with every photo selected.
The GDI Objects value keeps climbing until it reaches 10,000 then crash.
Selections do not need to be made all at once to reach this figure, it's cumulative,

Lightroom 5 crashes when I load track logs.

This is getting really annoying. I'm an aerial photographer. Every flight I do, I record a gpx track log, and marry the photos and GPS up in Lightroom. Works a treat, except that about 90% of the time, loading the track log causes Lightroom to crash. Then I have to restart, wait for my huge catalog to reload, re-select the day's shoot and load the track log again. This second attempt always works. It's not the end of the world, but it wastes time and is bloody annoying.
I know others have the same issue, but I've never seen any reasonable answer of fix.
Does anyone here know any more about this?

A number of people have reported such crashes for over a year in the official Adobe feedback forum:
Lightroom 4.3RC: Map crash
LR5.5 crashes in map module when loading track log
Lightroom 5.6 crashes on OSX if you load GPS track while building 1:1 previews
You might read through those posts to see if there are hints about triggers the crash (and that you could avoid). You might also add your opinion and vote, though I'm doubtful Adobe will address the issue any time in the near future.
Many people use Geosetter (as I do) or the Geoencoding Support plugin. The advantage of Geosetter is that it is widely used and quite robust; the disadvantage is that it's not as convenient as doing it directly in LR. I haven't used the Geoencoding Support plugin, though a number of people on these forums have reported being quite satisfied with it, and its author has an excellent reputation for his LR plugins.

Lightroom 5 crashing when straightening

Lightroom 5 hangs and crashes very regularly ( about ten times in an hour ) when I use the crop tool and straighten the image? I tried deleting the preferences, increasing the cache, creating a new catalogue.... it continues to crash.

Yep, I installed LR5 today on my;
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:          6 GB
Running OSX10.8.4.
In doing my first job I'm getting the beachball when rotating using the crop tool. Only solution is Force Quit.
No good. Seems quite a lethal bug. Glad I'm on a CC subscription, I'll flick back to LR4 but how does this stuff get released? Pretty ordinary seeing it looks a common problem.

Adobe Premiere CC Crashes When Selecting Multiple Clips

This project was already derailed by multicam, now that I've got my assembly edit ready to go, I've discovered a new show-stopper: Premiere Pro CC crashes when I select multiple clips on the timeline. I can't select more than 3 clips at a time, or the entire program comes crashing to it's knees. Anyone else experiencing something like this? Can anyone else reproduce this behavior?
Here's a video of the experience:
http://youtu.be/DPOUinOSzDE
Any word on an update?
ASUS G75VX
Windows 7 Pro, 64-bit
GTX 670MX, 3GB GDDR5
16GB RAM

Progress. I've been able to isolate the problem. On my timeline I have some "regular" clips and some "merged" clips. Regular clips are from either source: a Canon 7D (MP4 / MOV) or a Canon VIXIA HF G20 (AVCHD). The Merged clips are only from the Canon 7D only (for video) and an audio recorder (MP3 at 320kbps). The 7D footage is 1080/24p. The VIXIA also shoots in 24p.
Since "Merge Clips" sync on audio is not working for me, I've employed my former CS6 workflow:
1. Sync all of the video and audio clips through PluralEyes 3 resulting in a preliminary sequence, "Clips_to_be_merged_sequence".
2. I work my way through each of the clips, adjusting the audio track(s) for variances in drift between the on camera sound and the audio recorder. I do this enabling "Audio Time Units", rather than video frames, so I can get extremely acurate.
3. When I have a timeline full of nicely syncronized audio/video pairs, I merge clips, one painstaking clip at a time (of course I set up a keyboard shortcut for this). For the merge, I "sync on In points".
4. The merged clip is added to my project panel.
5. Now, when it comes time to choose my sound bite selects, I load the merged clip into the Source panel and mark my Ins and Outs.
6. Time to create a subclip, of course with the new SOFT handles. (I'VE BEEN WANTING SOFT HANDLES FOR A LONG TIME!!!)
7. The subclip appears to be properly created and placed into the Project panel. It even shows the correct duration (i.e. 14 seconds)
8. When I drag that subclip onto the timeline it drags the entire length of the parent clip, without in or out points (not just the 14 second subclip).
9. I undo and decide to go back through the original clips again; mark ins and outs and simply drop to the timeline (either Insert or Overwrite).
So in the end, I'm using sections of the Merged clip, but I'm not using Subclips of the Merged clips (because that doesn't work).
Now, what's happening, though I didn't know it when I recorded the video above, is that Premiere is crashing any time I select both "regular" footage and "merged" footage.
So, two bugs here:
1. Can't use Subclips that are derived from Merged clips in ANY timeline. Once dragged to the timeline it expands to the full duration of the original clip.
2. Can't select both "regular" and "merged" clips at the same time on the timeline.
JStrawn (staff) was kind enough to offer to take a look at some small sample files. But my interview clips are very long, and I'm concerned that if I export them, to make them shorter, they may not actually exibit the problems I'm having on the original clips.
Anyone else using this type of "Merge Clip" workflow that could reproduce either the subclip-from-merged-clip bug or the mixed-selection crash given the steps above?

Photoshop crashes when selecting File / Automate / Batch

Photoshop users still need a fix for Photoshop crashing whenever they select Batch.
I understand that Adobe staff has chosen to blame scanner drivers for the problem. And, I've read the discussions thru last year (very long and boring when all you want is a fix). But, I'm not settled on several things which do not add-up.
First, I'll review the symptoms for the sake of all interested readers. Photoshop users have reported Photoshop crashing whenever they select File / Automate / Batch from the menu for years. This problem got much worse (widespread) since the release of version 12.0.4. The problem apparently affects only those with Train compatible scanners and who installed Adobe's optional Twain plugin. I never read how anyone came to this conclusion, but scanner drivers are being blamed. The accepted work-around is to disable or remove Adobe's Twain plugin.
Second, I want to point out that Photoshop works normally when using the Twain plugin. I can scan images and they are imported directly into Photoshop without any problems. This was the case before the 12.0.4 update and is still the case now.
Third, I want to pose my most pressing question. What does selecting "Batch..." have to do with scanner drivers? In other words, what possibly could Photoshop be doing with scanner drivers when selecting "Batch..." that it does not do when actually does use the drivers?
Lastly, I'll point out that I am a software developer of over 30 years. So, I understand how it might somehow work out in the details that the source of the problem really is buggy scanner drivers. However, as a programmer with a lot of experience dealing with problems common in device driver API's, I know that good practice is to expect anything. If Photoshop begins a process that calls out to someone else's software API, it should cushion that call with proper exception error handling. All processes should execute with an "if all else fails" contention.

>> What does selecting "Batch..." have to do with scanner drivers?
When running the actions for the Batch command, Photoshop updates it's menu/command state to check which commands are enabled or disabled based on the document state being changed by the actions. Part of that update is calling the scanner interface to see what is available or not, and at that point some drivers crash. Since the crash occurs in third party code executed within Photoshop's context - there was not much Photoshop could do to recover (there was exception handling, but it couldn't work across OS and DLL boundaries).
In Photoshop CS6, we spent quite a bit of time figuring out why they were crashing (apparently there was some assumption about the application GUI state), and how we could avoid them crashing in those circumstances - and now CS6 avoids the crashes in the Batch command even with the TWAIN plugin and drivers are loaded.

Lightroom CC Crashes when selecting 1:1 crop

Similar Messages

Maybe you are looking for