Lightroom 2.1 freezes when using new Gradient tool. (Mac 10.5 Leopard)

In the Develop Module, when I click the Gradient tool and apply it to an image, the "Beach Ball" appears and program freezes. When I go to "force Quit" the application, I see: Lightroom (Not Responding).
Running on IMac 24", 2.4 intel, 2GB Ram.

I took the plunge and while I've only edited a small series of images - 2.1 RC appears to be usable - thank you, Adobe engineers. I haven't gone hunting bugs, but previously the bugs were hunting me. More like ambushing at every mouse click.
I wanted to quickly mention that this forum has some seriously trigger-happy Adobe defenders. I realize that there are annoying know nothings out there, that don't run well maintained systems and blame the first hiccup on Adobe, Apple, MS or whoever. But sometimes the code is bad. I was pretty unhappy after paying the upgrade and getting what I felt was a useless beta, but the sting in the tail was the pushback on the forum. I don't spend enough time here to know the regulars from the visitors, so maybe it's just the usual wacko brand loyalists dropping by.
Recap: 2 Macs running latest Leopard and LR1 with no probs. Loaned Adobe some $ so they could develop some software while I upgraded to LR2. Beachballs started raining down on me, I troubleshooted on one system, everything short of a system reinstall, LR2 still useless on both. Downgraded to LR 1.4 so I could deliver work to clients. After reading this thread I installed 2.1 RC and no more beachballs on both systems. I feel pretty comfortable on where to assign hiccup blame. I'm blaming myself too, for upgrading. Adobe isn't getting a dime from me for CS4 or LR3 unless Apple 'upgrades' me into it. Stability over features, ALWAYS.

Similar Messages

Lightroom 5.2 freezes when using the spot edit tool with Wacom Intuos 5

Hi,
   I've been using Photoshop 6.x with my Intuos 5 for almost a year and it's been great. I recently purchased Lightroom 5.2 only to discover that when I use the spot edit tool that it freezes when i use this tool as a brush. It starts off smooth, but after brushing across my area i want to clone/heal, Lightroom seems to freeze up, and the spot edit tool is unusable. I can lift my pen off the tablet and a few seconds later Lightroom comes back, but the tablet is basically unusable to me. The mouse works perfectly fine.
I've read other posts at the end of last year '12, that walks through some regedits and disabling some other tablet functions, but none of those work for me. Any suggestions would be appreciated.
Thanks Ed
Lightroom version: 5.2 [922700]
Operating system: Windows 7 Ultimate Edition
Version: 6.1 [7601]
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 2.7 GHz
Built-in memory: 16375.0 MB
Real memory available to Lightroom: 16375.0 MB
Real memory used by Lightroom: 429.4 MB (2.6%)
Virtual memory used by Lightroom: 403.7 MB
Memory cache size: 300.8 MB
Maximum thread count used by Camera Raw: 4
System DPI setting: 144 DPI
Desktop composition enabled: No
Displays: 1) 1920x1200
Adapter #1: Vendor : 1002
          Device : 9498
          Subsystem : 16031462
          Revision : 0
          Video Memory : 1005
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Speakers (Realtek High Definition Audio)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 44100
Build: LR5x20
CardID: 38040
Direct2DEnabled: false
GPUDevice: D3D
MaxTexture2DSize: 8192
OGLEnabled: true
Renderer: ATI Radeon HD 4600 Series
ShaderModel: 10.1
Vendor: AMD
VendorID: 4098
Version: 1002:9498:16031462:0000

I solved my own issue. I saw an article @ http://www.lightroomforums.net/showthread.php?19694-Spot-removal-tool-doesn-t-work-with-Wa com-Intuos-5-in-LR-5 that solved my issue.
Step 1:
Walcom Tablet Properties
Step 2:
Click on Customize and change the default line graph from this:
Step 3:
To this
Step 4:
Click OK.
After that, my spot edit tool stopped freezing in LR 5.2 while i was using my intuos 5 pen.
Prior to doing this, I also did the procedure listed here: http://forum.wacom.eu/viewtopic.php?f=10&t=8036
So it's possible that both need to be done in order for the freezing to stop. I hope this can help others.

Fireworks Crashes / Freezes When Using the Text Tool

Mac Octocore > OSX 10.6.1
Master Collection > Fireworks CS4
First I noticed the text box shift.Then Fireworks CS4 would freeze during any of the following:
• Resize grouped text
• Move text box
• Click on text box to edit with type tool
• Double-click on text box to edit with pointer tool
So I started a brand new file, but encountered the same outcome. Thus, Fireworks CS4 is currently useless if text is needed. I can create vector based objects, but just clicking on the canvas (or clicking the font menu) with the text tool freezes Fireworks CS4 instantly. I've had similar issues with Fireworks CS3 edition, but if I started a new file, I was at least able to use the text tool again and type. Now, I can't even recreate the file. I have to abandon Fireworks and use a combination of Photoshop and Illustrator before my timeline becomes even further behind.
I'm at a complete loss.
Neil

Open Fireworks
Open >New Document
Paste > image from clipboard (copied from Safari browser)
Skittles spinning wheel of unlove
report below:
Date/Time: 2009-10-19 11:55:48 -0400
OS Version: 10.6.1 (Build 10B504)
Architecture: x86_64
Report Version: 6
Command: Fireworks
Path: /Applications/Adobe Fireworks CS4/Adobe Fireworks
CS4.app/Contents/MacOS/Adobe Fireworks CS4
Version: Adobe Fireworks CS4 version "10.0.3.011" (10.0.3)
Parent: launchd
PID: 25588
Event: hang
Duration: 6.86s (sampling started after 2 seconds)
Steps: 48 (100ms sampling interval)
Pageins: 0
Pageouts: 0
Process: Adobe Fireworks CS4
Path: /Applications/Adobe Fireworks CS4/Adobe Fireworks
CS4.app/Contents/MacOS/Adobe Fireworks CS4
UID: 501
Process: Adobe Illustrator
Path: /Applications/Adobe Illustrator CS4/Adobe
Illustrator.app/Contents/MacOS/Adobe Illustrator
UID: 501
Process: Adobe InDesign CS4
Path: /Applications/Adobe InDesign CS4/Adobe InDesign
CS4.app/Contents/MacOS/Adobe InDesign CS4
UID: 501
Process: AdobeCrashDaemon
Path: /Applications/Adobe Fireworks CS4/Adobe Fireworks
CS4.app/Contents/Frameworks/AdobeCrashReporter.framework/Versions/A/
Resources/AdobeCrashDaemon.app/Contents/MacOS/AdobeCrashDaemon
UID: 501
Process: AdobeCrashDaemon
Path: /Applications/Adobe Dreamweaver CS4/Adobe Dreamweaver
CS4.app/Contents/Frameworks/AdobeCrashReporter.framework/Versions/A/
Resources/AdobeCrashDaemon.app/Contents/MacOS/AdobeCrashDaemon
UID: 501
Process: AdobeCrashDaemon
Path: /Applications/Adobe Illustrator CS4/Adobe
Illustrator.app/Contents/Frameworks/AdobeCrashReporter.framework/
Versions/A/Resources/AdobeCrashDaemon.app/Contents/MacOS/
AdobeCrashDaemon
UID: 501
Process: AdobeCrashDaemon
Path: /Applications/Adobe InDesign CS4/Adobe InDesign
CS4.app/Contents/Frameworks/AdobeCrashReporter.framework/Versions/A/
Resources/AdobeCrashDaemon.app/Contents/MacOS/AdobeCrashDaemon
UID: 501
Process: AirPort Base Station Agent
Path: /System/Library/CoreServices/AirPort Base Station
Agent.app/Contents/MacOS/AirPort Base Station Agent
UID: 501
 Thread 179e33d4
 User stack:
 48 ??? (in AirPort Base Station Agent + 5344)
 48 ??? (in AirPort Base Station Agent + 70666)
 48 CFRunLoopRun + 70 (in CoreFoundation)
 48 CFRunLoopRunSpecific + 575 (in CoreFoundation)
 48 __CFRunLoopRun + 2002 (in CoreFoundation)
 48 mach_msg_trap + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 ipc_mqueue_receive_continue + 0
 Thread 179f63d4
 User stack:
 48 start_wqthread + 13 (in libSystem.B.dylib)
 48 pthreadwqthread + 353 (in libSystem.B.dylib)
 48 dispatchworker_thread2 + 244 (in libSystem.B.dylib)
 48 dispatchqueue_invoke + 195 (in libSystem.B.dylib)
 48 kevent + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 kevent + 97
 Thread 1d0ad7a8
 User stack:
 48 thread_start + 13 (in libSystem.B.dylib)
 48 pthreadstart + 331 (in libSystem.B.dylib)
 48 ??? (in AirPort Base Station Agent + 71314)
 48 ??? (in AirPort Base Station Agent + 13712)
 48 ??? (in AirPort Base Station Agent + 71484)
 48 __semwait_signal + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 semaphore_wait_continue + 0
 Thread 1d0adb7c
 User stack:
 48 thread_start + 13 (in libSystem.B.dylib)
 48 pthreadstart + 331 (in libSystem.B.dylib)
 48 select$DARWIN_EXTSN + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 sleep + 52
 Binary Images:
 0x100000000 - 0x100016fff
com.apple.AirPortBaseStationAgent 1.5.4 (154.2) <73DF13C1-AF86-
EC2C-9056-8D1946E607CF> /System/Library/CoreServices/AirPort Base
Station Agent.app/Contents/MacOS/AirPort Base Station Agent
 0x7fff82fd6000 - 0x7fff83149fef com.apple.CoreFoundation
6.6 (550) <04EC0CC2-6CE4-4EE0-03B9-6C5109398CB1> /System/Library/
Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
 0x7fff85e67000 - 0x7fff86025ff7 libSystem.B.dylib ???
(???) <66102D4E-6C8B-77D0-6766-2A1788B20C6F> /usr/lib/libSystem.B.dylib
Process: AppleSpell
Path: /System/Library/Services/AppleSpell.service/Contents/
MacOS/AppleSpell
UID: 501
 Thread 179eeb7c
 User stack:
 48 ??? (in AppleSpell + 5976)
 48 ??? (in AppleSpell + 6632)
 48 -[NSSpellServer run] + 72 (in Foundation)
 48 CFRunLoopRun + 70 (in CoreFoundation)
 48 CFRunLoopRunSpecific + 575 (in CoreFoundation)
 48 __CFRunLoopRun + 2002 (in CoreFoundation)
 48 mach_msg_trap + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 ipc_mqueue_receive_continue + 0
 Thread 1f3f03d4
 User stack:
 48 start_wqthread + 13 (in libSystem.B.dylib)
 48 pthreadwqthread + 353 (in libSystem.B.dylib)
 48 dispatchworker_thread2 + 244 (in libSystem.B.dylib)
 48 dispatchqueue_invoke + 195 (in libSystem.B.dylib)
 48 kevent + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 kevent + 97
 Binary Images:
 0x100000000 - 0x1000a9fef com.apple.AppleSpell 1.6
(61) <9297064E-04F0-2CBF-0A16-6050010DAC3D> /System/Library/Services/
AppleSpell.service/Contents/MacOS/AppleSpell
 0x7fff82fd6000 - 0x7fff83149fef com.apple.CoreFoundation
6.6 (550) <04EC0CC2-6CE4-4EE0-03B9-6C5109398CB1> /System/Library/
Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
 0x7fff84b9f000 - 0x7fff84e20fe7 com.apple.Foundation 6.6
(751) <CCE98C5C-DFEA-6C80-A014-A5985437072E> /System/Library/
Frameworks/Foundation.framework/Versions/C/Foundation
 0x7fff85e67000 - 0x7fff86025ff7 libSystem.B.dylib ???
(???) <66102D4E-6C8B-77D0-6766-2A1788B20C6F> /usr/lib/libSystem.B.dylib
Process: autofsd
Path: /usr/libexec/autofsd
UID: 0
 Thread 1748e7a8
 User stack:
 48 ??? (in autofsd + 5340)
 48 ??? (in autofsd + 6461)
 48 CFRunLoopRun + 70 (in CoreFoundation)
 48 CFRunLoopRunSpecific + 575 (in CoreFoundation)
 48 __CFRunLoopRun + 2002 (in CoreFoundation)
 48 mach_msg_trap + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 ipc_mqueue_receive_continue + 0
 Thread 17500000 DispatchQueue 2
 User stack:
 48 start_wqthread + 13 (in libSystem.B.dylib)
 48 pthreadwqthread + 353 (in libSystem.B.dylib)
 48 dispatchworker_thread2 + 244 (in libSystem.B.dylib)
 48 dispatchqueue_invoke + 195 (in libSystem.B.dylib)
 48 kevent + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 kevent + 97
 Binary Images:
 0x100000000 - 0x100001ff7 autofsd ??? (???)
<29276FAC-AEA8-1520-5329-C75F9D453D6C> /usr/libexec/autofsd
 0x7fff82fd6000 - 0x7fff83149fef com.apple.CoreFoundation
6.6 (550) <04EC0CC2-6CE4-4EE0-03B9-6C5109398CB1> /System/Library/
Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
 0x7fff85e67000 - 0x7fff86025ff7 libSystem.B.dylib ???
(???) <66102D4E-6C8B-77D0-6766-2A1788B20C6F> /usr/lib/libSystem.B.dylib
Process: blued
Path: /usr/sbin/blued
UID: 0
 Thread 1748eb7c
 User stack:
 48 ??? (in blued + 6232)
 48 ??? (in blued + 130148)
 48 -[NSRunLoop(NSRunLoop) run] + 77 (in Foundation)
 48 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 270 (in
Foundation)
 48 CFRunLoopRunSpecific + 575 (in CoreFoundation)
 48 __CFRunLoopRun + 2002 (in CoreFoundation)
 48 mach_msg_trap + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 ipc_mqueue_receive_continue + 0
 Thread 175713d4 DispatchQueue 2
 User stack:
 48 start_wqthread + 13 (in libSystem.B.dylib)
 48 pthreadwqthread + 353 (in libSystem.B.dylib)
 48 dispatchworker_thread2 + 244 (in libSystem.B.dylib)
 48 dispatchqueue_invoke + 195 (in libSystem.B.dylib)
 48 kevent + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 kevent + 97
 Binary Images:
 0x100000000 - 0x10003bfff blued ??? (???)
<2155B8CF-9765-0B49-3B94-1EFF788A2A2B> /usr/sbin/blued
 0x7fff82fd6000 - 0x7fff83149fef com.apple.CoreFoundation
6.6 (550) <04EC0CC2-6CE4-4EE0-03B9-6C5109398CB1> /System/Library/
Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
 0x7fff84b9f000 - 0x7fff84e20fe7 com.apple.Foundation 6.6
(751) <CCE98C5C-DFEA-6C80-A014-A5985437072E> /System/Library/
Frameworks/Foundation.framework/Versions/C/Foundation
 0x7fff85e67000 - 0x7fff86025ff7 libSystem.B.dylib ???
(???) <66102D4E-6C8B-77D0-6766-2A1788B20C6F> /usr/lib/libSystem.B.dylib
Process: Calculator
Path: /Applications/Calculator.app/Contents/MacOS/Calculator
UID: 501
 Thread 1e616000
 User stack:
 48 ??? (in Calculator + 6464)
 48 NSApplicationMain + 364 (in AppKit)
 48 -[NSApplication run] + 395 (in AppKit)
 48 -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:] + 155 (in AppKit)
 48 _DPSNextEvent + 718 (in AppKit)
 48 BlockUntilNextEventMatchingListInMode + 59 (in
HIToolbox)
 48 ReceiveNextEventCommon + 310 (in HIToolbox)
 48 RunCurrentEventLoopInMode + 333 (in HIToolbox)
 48 CFRunLoopRunSpecific + 575 (in CoreFoundation)
 48 __CFRunLoopRun + 2002 (in CoreFoundation)
 48 mach_msg_trap + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 ipc_mqueue_receive_continue + 0
 Thread 29fca7a8
 User stack:
 48 start_wqthread + 13 (in libSystem.B.dylib)
 48 pthreadwqthread + 353 (in libSystem.B.dylib)
 48 dispatchworker_thread2 + 244 (in libSystem.B.dylib)
 48 dispatchqueue_invoke + 195 (in libSystem.B.dylib)
 48 kevent + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 kevent + 97
 Thread 2a2ba7a8
 User stack:
 48 thread_start + 13 (in libSystem.B.dylib)
 48 pthreadstart + 331 (in libSystem.B.dylib)
 48 startIOThread(void*) + 139 (in CoreVideo)
 48 CVDisplayLink::runIOThread() + 739 (in CoreVideo)
 48 __semwait_signal + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 semaphore_wait_continue + 0
 Binary Images:
 0x100000000 - 0x100015fff com.apple.calculator 4.5.2
(97) <630F388E-CE64-0DB8-18E7-39A0D3DA0A05> /Applications/
Calculator.app/Contents/MacOS/Calculator
 0x7fff81fc3000 - 0x7fff829b7fe7 com.apple.AppKit 6.6.1
(1038.2) <C17AD2AC-8639-D20F-CD99-36EEC619A5F0> /System/Library/
Frameworks/AppKit.framework/Versions/C/AppKit
 0x7fff82fd6000 - 0x7fff83149fef com.apple.CoreFoundation
6.6 (550) <04EC0CC2-6CE4-4EE0-03B9-6C5109398CB1> /System/Library/
Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
 0x7fff85e67000 - 0x7fff86025ff7 libSystem.B.dylib ???
(???) <66102D4E-6C8B-77D0-6766-2A1788B20C6F> /usr/lib/libSystem.B.dylib
 0x7fff86ebe000 - 0x7fff86ee2ff7 com.apple.CoreVideo 1.6.0
(43.0) <FF5F0EEF-56BE-24DD-C8FA-CB41F126E6A8> /System/Library/
Frameworks/CoreVideo.framework/Versions/A/CoreVideo
 0x7fff86fe4000 - 0x7fff872e1fef com.apple.HIToolbox 1.6.0
(???) <870B39B2-55BD-9C82-72EB-2E3470BD0E14> /System/Library/
Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/
Versions/A/HIToolbox
Process: configd
Path: /usr/libexec/configd
UID: 0
 Thread 16cb8000
 User stack:
 48 start + 52 (in configd)
 48 main + 2051 (in configd)
 48 server_loop + 72 (in configd)
 48 CFRunLoopRunSpecific + 575 (in CoreFoundation)
 48 __CFRunLoopRun + 2002 (in CoreFoundation)
 48 mach_msg_trap + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 ipc_mqueue_receive_continue + 0
 Thread 16c23b7c DispatchQueue 2
 User stack:
 48 start_wqthread + 13 (in libSystem.B.dylib)
 48 pthreadwqthread + 353 (in libSystem.B.dylib)
 48 dispatchworker_thread2 + 244 (in libSystem.B.dylib)
 48 dispatchqueue_invoke + 195 (in libSystem.B.dylib)
 48 kevent + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 kevent + 97
 Thread 16c2f000
 User stack:
 48 thread_start + 13 (in libSystem.B.dylib)
 48 pthreadstart + 331 (in libSystem.B.dylib)
 48 plugin_exec + 1440 (in configd)
 48 CFRunLoopRun + 70 (in CoreFoundation)
 48 CFRunLoopRunSpecific + 575 (in CoreFoundation)
 48 __CFRunLoopRun + 2002 (in CoreFoundation)
 48 mach_msg_trap + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 ipc_mqueue_receive_continue + 0
 Thread 1733a7a8
 User stack:
 48 thread_start + 13 (in libSystem.B.dylib)
 48 pthreadstart + 331 (in libSystem.B.dylib)
 48 iopm_force_active_settings + 2266 (in PowerManagement)
 48 CFRunLoopRun + 70 (in CoreFoundation)
 48 CFRunLoopRunSpecific + 575 (in CoreFoundation)
 48 __CFRunLoopRun + 2002 (in CoreFoundation)
 48 mach_msg_trap + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 ipc_mqueue_receive_continue + 0
 Thread 1739e7a8
 User stack:
 48 thread_start + 13 (in libSystem.B.dylib)
 48 pthreadstart + 331 (in libSystem.B.dylib)
 48 select$DARWIN_EXTSN + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 sleep + 52
 Thread 17686000
 User stack:
 48 start_wqthread + 13 (in libSystem.B.dylib)
 48 __workq_kernreturn + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 workqueue_thread_yielded + 562
 Binary Images:
 0x100000000 - 0x100026ff7 configd ??? (???)
<9ED4C5BD-86FA-DE9B-A948-8BE9ADE9005F> /usr/libexec/configd
 0x100489000 - 0x10049afff
com.apple.SystemConfiguration.PowerManagement 160.0.0 (160.0.0)
<42FFC4FD-5D78-F476-2A4E-015951986425> /System/Library/
SystemConfiguration/PowerManagement.bundle/Contents/MacOS/
PowerManagement
 0x7fff82fd6000 - 0x7fff83149fef com.apple.CoreFoundation
6.6 (550) <04EC0CC2-6CE4-4EE0-03B9-6C5109398CB1> /System/Library/
Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
 0x7fff85e67000 - 0x7fff86025ff7 libSystem.B.dylib ???
(???) <66102D4E-6C8B-77D0-6766-2A1788B20C6F> /usr/lib/libSystem.B.dylib
Process: coreaudiod
Path: /usr/sbin/coreaudiod
UID: 202
 Thread 173b7000
 User stack:
 48 ??? (in coreaudiod + 3312)
 48 ??? (in coreaudiod + 26565)
 48 CFRunLoopRunSpecific + 575 (in CoreFoundation)
 48 __CFRunLoopRun + 2002 (in CoreFoundation)
 48 mach_msg_trap + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 ipc_mqueue_receive_continue + 0
 Thread 179f53d4 DispatchQueue
 User stack:
 48 start_wqthread + 13 (in libSystem.B.dylib)
 48 pthreadwqthread + 353 (in libSystem.B.dylib)
 48 dispatchworker_thread2 + 244 (in libSystem.B.dylib)
 48 dispatchqueue_invoke + 195 (in libSystem.B.dylib)
 48 kevent + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 kevent + 97
 Thread 1ce0f000
 User stack:
 48 start_wqthread + 13 (in libSystem.B.dylib)
 48 __workq_kernreturn + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 workqueue_thread_yielded + 562
 Binary Images:
 0x100000000 - 0x10001ffef coreaudiod ??? (???)
<8580E560-986B-5336-B8B7-968C3E7C22A2> /usr/sbin/coreaudiod
 0x7fff82fd6000 - 0x7fff83149fef com.apple.CoreFoundation
6.6 (550) <04EC0CC2-6CE4-4EE0-03B9-6C5109398CB1> /System/Library/
Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
 0x7fff85e67000 - 0x7fff86025ff7 libSystem.B.dylib ???
(???) <66102D4E-6C8B-77D0-6766-2A1788B20C6F> /usr/lib/libSystem.B.dylib
Process: coreservicesd
Path: /System/Library/CoreServices/coreservicesd
UID: 0
 Thread 175b2000
 User stack:
 48 ??? (in coreservicesd + 3756)
 48 _CoreServicesServerMain + 522 (in CarbonCore)
 48 CFRunLoopRun + 70 (in CoreFoundation)
 48 CFRunLoopRunSpecific + 575 (in CoreFoundation)
 48 __CFRunLoopRun + 2002 (in CoreFoundation)
 48 mach_msg_trap + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 ipc_mqueue_receive_continue + 0
 Thread 174407a8
 User stack:
 47 start_wqthread + 13 (in libSystem.B.dylib)
 47 __workq_kernreturn + 10 (in libSystem.B.dylib)
 Kernel stack:
 47 workqueue_thread_yielded + 562
 1 thread_bootstrap_return + 0
 Thread 17686b7c
 User stack:
 48 start_wqthread + 13 (in libSystem.B.dylib)
 48 pthreadwqthread + 353 (in libSystem.B.dylib)
 48 dispatchworker_thread2 + 244 (in libSystem.B.dylib)
 48 dispatchqueue_invoke + 195 (in libSystem.B.dylib)
 48 kevent + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 kevent + 97
 Thread 17999000
 User stack:
 48 thread_start + 13 (in libSystem.B.dylib)
 48 pthreadstart + 331 (in libSystem.B.dylib)
 48 read + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 lo64_unix_scall + 77
 48 unix_syscall64 + 617
 48 read_nocancel + 158
 48 write + 312
 48 get_pathbuff + 3054
 48 tsleep + 105
 48 wakeup + 786
 48 thread_block + 33
 48 thread_block_reason + 331
 48 thread_dispatch + 1949
 48 machine_switch_context + 753
 Thread 179993d4
 User stack:
 48 thread_start + 13 (in libSystem.B.dylib)
 48 pthreadstart + 331 (in libSystem.B.dylib)
 48 fmodWatchConsumer + 347 (in CarbonCore)
 48 __semwait_signal + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 semaphore_wait_continue + 0
 Binary Images:
 0x100000000 - 0x100000fff coreservicesd ??? (???)
<04B17F9C-7722-BE56-2850-868C11D34FF9> /System/Library/CoreServices/
coreservicesd
 0x7fff82fd6000 - 0x7fff83149fef com.apple.CoreFoundation
6.6 (550) <04EC0CC2-6CE4-4EE0-03B9-6C5109398CB1> /System/Library/
Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
 0x7fff8338f000 - 0x7fff836c1fef
com.apple.CoreServices.CarbonCore 859.1 (859.1) <5712C4C1-
B18B-88EE-221F-DA04A8EDA029> /System/Library/Frameworks/
CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/
Versions/A/CarbonCore
 0x7fff85e67000 - 0x7fff86025ff7 libSystem.B.dylib ???
(???) <66102D4E-6C8B-77D0-6766-2A1788B20C6F> /usr/lib/libSystem.B.dylib
Process: cvmsServ
Path: /System/Library/Frameworks/OpenGL.framework/Versions/
A/Libraries/cvmsServ
UID: 0
 Thread 179ed3d4 DispatchQueue 1
 User stack:
 48 ??? (in cvmsServ + 4100)
 48 ??? (in cvmsServ + 23081)
 48 mach_msg_server + 597 (in libSystem.B.dylib)
 48 mach_msg_trap + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 ipc_mqueue_receive_continue + 0
 Binary Images:
 0x100000000 - 0x100008fff cvmsServ ??? (???)
<8B29F0EA-273E-D990-D755-F64A6773BF83> /System/Library/Frameworks/
OpenGL.framework/Versions/A/Libraries/cvmsServ
 0x7fff85e67000 - 0x7fff86025ff7 libSystem.B.dylib ???
(???) <66102D4E-6C8B-77D0-6766-2A1788B20C6F> /usr/lib/libSystem.B.dylib
Process: DashboardClient
Path: /System/Library/CoreServices/Dock.app/Contents/
Resources/DashboardClient.app/Contents/MacOS/DashboardClient
UID: 501
 Thread 208dcb7c
 User stack:
 48 ??? (in DashboardClient + 4992)
 48 ??? (in DashboardClient + 20081)
 48 -[NSApplication run] + 395 (in AppKit)
 48 -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:] + 155 (in AppKit)
 48 _DPSNextEvent + 718 (in AppKit)
 48 BlockUntilNextEventMatchingListInMode + 59 (in
HIToolbox)
 48 ReceiveNextEventCommon + 310 (in HIToolbox)
 48 RunCurrentEventLoopInMode + 333 (in HIToolbox)
 48 CFRunLoopRunSpecific + 575 (in CoreFoundation)
 48 __CFRunLoopRun + 2002 (in CoreFoundation)
 48 mach_msg_trap + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 ipc_mqueue_receive_continue + 0
 Thread 179f47a8
 User stack:
 48 thread_start + 13 (in libSystem.B.dylib)
 48 pthreadstart + 331 (in libSystem.B.dylib)
 48 select$DARWIN_EXTSN + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 sleep + 52
 Thread 1e4bd7a8
 User stack:
 48 thread_start + 13 (in libSystem.B.dylib)
 48 pthreadstart + 331 (in libSystem.B.dylib)
 48 __NSThread__main__ + 1429 (in Foundation)
 48 +[NSURLConnection(NSURLConnectionReallyInternal)
_resourceLoadLoop:] + 297 (in Foundation)
 48 CFRunLoopRunSpecific + 575 (in CoreFoundation)
 48 __CFRunLoopRun + 2002 (in CoreFoundation)
 48 mach_msg_trap + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 ipc_mqueue_receive_continue + 0
 Thread 20780b7c
 User stack:
 48 start_wqthread + 13 (in libSystem.B.dylib)
 48 pthreadwqthread + 353 (in libSystem.B.dylib)
 48 dispatchworker_thread2 + 244 (in libSystem.B.dylib)
 48 dispatchqueue_invoke + 195 (in libSystem.B.dylib)
 48 kevent + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 kevent + 97
 Thread 29fb87a8
 User stack:
 48 start_wqthread + 13 (in libSystem.B.dylib)
 48 __workq_kernreturn + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 workqueue_thread_yielded + 562
 Binary Images:
 0x100000000 - 0x100006fff com.apple.dashboard.client
1.7 (1.7) <C030A9A7-3A76-8829-7062-F9ACAC8B361A> /System/Library/
CoreServices/Dock.app/Contents/Resources/DashboardClient.app/Contents/
MacOS/DashboardClient
 0x7fff81fc3000 - 0x7fff829b7fe7 com.apple.AppKit 6.6.1
(1038.2) <C17AD2AC-8639-D20F-CD99-36EEC619A5F0> /System/Library/
Frameworks/AppKit.framework/Versions/C/AppKit
 0x7fff82fd6000 - 0x7fff83149fef com.apple.CoreFoundation
6.6 (550) <04EC0CC2-6CE4-4EE0-03B9-6C5109398CB1> /System/Library/
Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
 0x7fff84b9f000 - 0x7fff84e20fe7 com.apple.Foundation 6.6
(751) <CCE98C5C-DFEA-6C80-A014-A5985437072E> /System/Library/
Frameworks/Foundation.framework/Versions/C/Foundation
 0x7fff85e67000 - 0x7fff86025ff7 libSystem.B.dylib ???
(???) <66102D4E-6C8B-77D0-6766-2A1788B20C6F> /usr/lib/libSystem.B.dylib
 0x7fff86fe4000 - 0x7fff872e1fef com.apple.HIToolbox 1.6.0
(???) <870B39B2-55BD-9C82-72EB-2E3470BD0E14> /System/Library/
Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/
Versions/A/HIToolbox
Process: Dictionary
Path: /Applications/Dictionary.app/Contents/MacOS/Dictionary
UID: 501
 Thread 1ce307a8
 User stack:
 48 ??? (in Dictionary + 4916)
 48 NSApplicationMain + 364 (in AppKit)
 48 -[NSApplication run] + 395 (in AppKit)
 48 -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:] + 155 (in AppKit)
 48 _DPSNextEvent + 718 (in AppKit)
 48 BlockUntilNextEventMatchingListInMode + 59 (in
HIToolbox)
 48 ReceiveNextEventCommon + 310 (in HIToolbox)
 48 RunCurrentEventLoopInMode + 333 (in HIToolbox)
 48 CFRunLoopRunSpecific + 575 (in CoreFoundation)
 48 __CFRunLoopRun + 2002 (in CoreFoundation)
 48 mach_msg_trap + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 ipc_mqueue_receive_continue + 0
 Thread 1e4bdb7c
 User stack:
 48 thread_start + 13 (in libSystem.B.dylib)
 48 pthreadstart + 331 (in libSystem.B.dylib)
 48 __NSThread__main__ + 1429 (in Foundation)
 48 +[NSURLConnection(NSURLConnectionReallyInternal)
_resourceLoadLoop:] + 297 (in Foundation)
 48 CFRunLoopRunSpecific + 575 (in CoreFoundation)
 48 __CFRunLoopRun + 2002 (in CoreFoundation)
 48 mach_msg_trap + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 ipc_mqueue_receive_continue + 0
 Thread 204263d4
 User stack:
 48 start_wqthread + 13 (in libSystem.B.dylib)
 48 pthreadwqthread + 353 (in libSystem.B.dylib)
 48 dispatchworker_thread2 + 244 (in libSystem.B.dylib)
 48 dispatchqueue_invoke + 195 (in libSystem.B.dylib)
 48 kevent + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 kevent + 97
 Thread 285ddb7c
 User stack:
 48 start_wqthread + 13 (in libSystem.B.dylib)
 48 __workq_kernreturn + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 workqueue_thread_yielded + 562
 Thread 2a2b6b7c
 User stack:
 48 thread_start + 13 (in libSystem.B.dylib)
 48 pthreadstart + 331 (in libSystem.B.dylib)
 48 select$DARWIN_EXTSN + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 sleep + 52
 Binary Images:
 0x100000000 - 0x100034ff7 com.apple.Dictionary 2.1
(80) <768C3606-D309-99B2-3B1D-EB01CB189683> /Applications/
Dictionary.app/Contents/MacOS/Dictionary
 0x7fff81fc3000 - 0x7fff829b7fe7 com.apple.AppKit 6.6.1
(1038.2) <C17AD2AC-8639-D20F-CD99-36EEC619A5F0> /System/Library/
Frameworks/AppKit.framework/Versions/C/AppKit
 0x7fff82fd6000 - 0x7fff83149fef com.apple.CoreFoundation
6.6 (550) <04EC0CC2-6CE4-4EE0-03B9-6C5109398CB1> /System/Library/
Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
 0x7fff84b9f000 - 0x7fff84e20fe7 com.apple.Foundation 6.6
(751) <CCE98C5C-DFEA-6C80-A014-A5985437072E> /System/Library/
Frameworks/Foundation.framework/Versions/C/Foundation
 0x7fff85e67000 - 0x7fff86025ff7 libSystem.B.dylib ???
(???) <66102D4E-6C8B-77D0-6766-2A1788B20C6F> /usr/lib/libSystem.B.dylib
 0x7fff86fe4000 - 0x7fff872e1fef com.apple.HIToolbox 1.6.0
(???) <870B39B2-55BD-9C82-72EB-2E3470BD0E14> /System/Library/
Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/
Versions/A/HIToolbox
Process: DirectoryService
Path: /usr/sbin/DirectoryService
UID: 0
 Thread 1733ab7c
 User stack:
 48 start + 52 (in DirectoryService)
 48 main + 3086 (in DirectoryService)
 48 CFRunLoopRun + 70 (in CoreFoundation)
 48 CFRunLoopRunSpecific + 575 (in CoreFoundation)
 48 __CFRunLoopRun + 2002 (in CoreFoundation)
 48 mach_msg_trap + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 ipc_mqueue_receive_continue + 0
 Thread 173a57a8 DispatchQueue
 User stack:
 48 start_wqthread + 13 (in libSystem.B.dylib)
 48 pthreadwqthread + 353 (in libSystem.B.dylib)
 48 dispatchworker_thread2 + 231 (in libSystem.B.dylib)
 48 dispatchcall_block_and_release + 15 (in
libSystem.B.dylib)
 48 syscall + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 sleep + 52
 Thread 173b7b7c DispatchQueue
 User stack:
 48 start_wqthread + 13 (in libSystem.B.dylib)
 48 pthreadwqthread + 353 (in libSystem.B.dylib)
 48 dispatchworker_thread2 + 244 (in libSystem.B.dylib)
 48 dispatchqueue_invoke + 195 (in libSystem.B.dylib)
 48 kevent + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 kevent + 97
 Thread 173a53d4
 User stack:
 48 thread_start + 13 (in libSystem.B.dylib)
 48 pthreadstart + 331 (in libSystem.B.dylib)
 48 DSLThread::_RunWrapper(void*) + 67 (in
DirectoryServiceCore)
 48 DSCThread::Run() + 36 (in DirectoryServiceCore)
 48 CPluginRunLoopThread::ThreadMain() + 150 (in
DirectoryService)
 48 CFRunLoopRun + 70 (in CoreFoundation)
 48 CFRunLoopRunSpecific + 575 (in CoreFoundation)
 48 __CFRunLoopRun + 2002 (in CoreFoundation)
 48 mach_msg_trap + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 ipc_mqueue_receive_continue + 0
 Thread 1d09d3d4
 User stack:
 Kernel stack:
 48 thread_bootstrap_return + 0
 Thread 1f3e8000
 User stack:
 48 start_wqthread + 13 (in libSystem.B.dylib)
 48 __workq_kernreturn + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 workqueue_thread_yielded + 562
 Thread 2a2aab7c
 User stack:
 48 start_wqthread + 13 (in libSystem.B.dylib)
 48 __workq_kernreturn + 10 (in libSystem.B.dylib)
 Kernel stack:
 48 workqueue_thread_yielded + 562
 Binary Images:
 0x100000000 - 0x100120fff DirectoryService ??? (???)
<F6A2E16D-2B8F-DE6D-FA55-B2B21EB38B9B> /usr/sbin/DirectoryService
 0x100170000 - 0x100181fff
com.apple.DirectoryServiceCore.Framework 3.6 (621)
<ECBA2170-0C45-2E48-64CE-22EEBA4FF07C> /System/Library/
PrivateFrameworks/DirectoryServiceCore.framework/Versions/A/
DirectoryServiceCore
 0x7fff82fd6000 - 0x7fff83149fef com.apple.CoreFoundation
6.6 (550) <04EC0CC2-6CE4-4EE0-03B9-6C5109398CB1> /System/Library/
Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
 0x7fff85e67000 - 0x7fff86025ff7 libSystem.B.dylib ???
(???) <66102D4E-6C8B-77D0-6766-2A1788B20C6F> /usr/lib/libSystem.B.dylib
Process: diskarbitrationd
Path: /usr/sbin/diskarbitrationd
UID: 0
 Thread 16c65b7c
 User stack:
 48 ??? (in diskarbitrationd + 4064)
 48 ??? (in diskarbitrationd + 32876)
 48 CFRunLoopRun + 70 (in CoreFoundation)
 48 CFRunLoopRunSpecific + 575 (in CoreFoundation)
 48 __CFRunLoopRun + 2002 (in CoreFoundation)

After Effects CS6 11.0.2 crashes when using the pen tool (Mac OS X 10.8.2)

I'm using After Effects CS6 11.0.2 on Mac OS X 10.8.2. Whenever I use the pen tool to add a vertex, the application crashes. I've submitted several crash reports to apple (they get sent to apple automatically when the app relaunches).
My specs:
iMac
21.5-inch, Mid 2010
Processor 3.06 GHz Intel Core i3
Memory 12 GB 1333 MHz DDR3
Graphics ATI Radeon HD 4670 256 MB
Software OS X 10.8.2 (12C60)
Anybody else having this problem or have a solution?

So I have discovered it only crashes when adding a vertex when I'm editing the max a few frames in. When I add vertices on the first frame of the comp I don't have any trouble. I've tried unchecking the box that says preserve constant vertex count, and it still happens.

Disk Utility Freeze when using New Image

Has anybody experienced the following?:
my system:
Brand new Mac Pro 8-core 2.66GHz
24GB RAM
Snow Leopard 10.6.3 freshly installed
Apple SuperDrive DVD
I am in the process to install a lot of software and I like to make Disk Image of the software DVD to make things quicker to install.
Now what happens is that as soon as I select New Image from Disk Utility (after selecting the DVD on the left menu), the New Image progress window appears and then Disk Utility freezes. The disk image is being created in the background, but the progress window DOES NOT show the disk image status and eventually I have to OPTION-APPLE ESC from Disk Utility.
What I have tried is:
. delete plist for Disk Utility in Preferences
. repair permissions in SAFE BOOT mode
After that Disk Utility/New Image will work the first time as expected, and then the next time I am getting the same problem.
Any ideas what I could try to diagnose/fix this problem?
Thank you!

Thanks for your feedback.
As far as making a disk image or not, yes it takes some times to create it... longer? I am not sure because when you install a software there is a back and forth reading/writing, whereas when you create your disk image it does the reading and writing in a linear fashion... anyway to me the big benefit is when you have more than one disk part of an install (Apple FCS, Adobe CS, etc...) once you have created all your disk image, it will install everything automatically without having to feed each disc... and usually I have to do a fresh install later on... and finally it gives you a backup of your software...
Thanks again.

My Mac completely seizes when using the Gradient Tool in Photoshop CS5

I've recently upgraded to CS5 and in tandem have replaced my 8Gb of RAM with 16Gb on an iMac 27" with a 2.8Ghz Intel Core i7.
The problem that I've encountered with Photoshop seems to be connected with the COMBINED effect of these two upgrades. I just need to determine where the problem lies.
Whilst attempting to apply a gradient (white to transparent) using Photoshop CS5 on a CMYK file my Mac completely seizes. And I mean completely! No 'force quit' option, nothing. Even the little light on my mouse goes out. However, suspecting that it may be a CS5 problem I tried the same procedure using CS4. Hey presto – no problem. Narrowing the area down still further I re-installed the original 8Gb chips and the problem went away. Back to the 16Gb and the problem reoccurs. I've also found that using the 'Auto Merge' facility also causes the same seizure.
So, is it a RAM problem or a CS5 problem or a combination of the two? I've run Memtest the result of which indicated that the new RAM was behaving itself. The new memory is Kingston's finest and has had no adverse effects anywhere else on the system. If anyone can come up with a definitive answer I'd be grateful, especially if it means I can get my memory supplier to exchange my purchase gratis.

If the whole machine freezes, then you are most likely looking at a hardware problem.
Narrowing the area down still further I re-installed the original 8Gb chips and the problem went away.
Yep, that's more evidence that the problem is in your hardware.
Application software cannot cause a lockup like that. Only hardware, low level drivers and the OS can cause a lockup like that.
In your case, it seems to be the hardware (RAM chips or motherboard).
Unfortunately, software RAM tests are useless. But you've got a test that stresses the RAM system more than those tests: it's called Photoshop.
We have seen several reports recently of RAM problems in newer iMacs. There appears to be a problem with the RAM specification, testing, or the motherboards. Unfortunately, we don't yet have enough details to determine the root cause of the issues. But most people have fixed the problem by swapping out the RAM.

Poor Lightroom 5.7 Performance when using part repair tool

Hi Lightroom pros,
I'm using Lightroom 5.7 for about half a year and are very happy with it. Unless I'm working on photos where I have to use the part repairt tool to much.
I'm specialized in car photograpy and often have to remove dust from the cars paint work and chrome. When I have to work on hughe areas Lightroom becomes slower and slower. I read that the repair tool costs a lot of performance but I'm wondering if I could optimize something or if there is a workaround for that? Because right now its not usable doing one click and waiting 2 minutes...
I'm using the newest Lightroom 64-bit version on a Windows 8.1 Enterprise 64-bit Laptop with an internal SSD drive. LR is installed on that drive and the Catalogue also is stored there. I have 70 GB of free space on that drive, my catalogue is around 5 GB, my Camera Raw Cache Size is 20 GB.
The machine has 16 GB of RAM and an Intel Core i7 3 GHz Quadcore processor. My RAW files are stored on an external USB 3.0 Drive (not SSD).
When working on that kind of picutres I usually close as much programms as possible, so that most of the time LR is the only working desktop programm. What seems strange to me is, that even if I'm waiting for minutes for LR to answer, that my processor and RAM are only using about 40% of it's power. The rest seems not to be used by LR?!
I would be really thankful for tipps or ideas how to improve that issue because right now I'm really wasting a lot of time.
Kind regards
Torsten

I guess this depends on what you are doing, what type of original files you are using, and your own perception of quality. I would believe that in most cases, if you do all the editing in LR except for the spot removal, get the photo to appear the way you want (except for the spot removal), and then lastly move it to PSE and remove the spots, that there isn't really any noticeable loss of quality.
I must admit I'm not a pro concerning color managment. But I already downloaded the PSE testversion and realized that it is not capable to deal with 16-bit color depth. Wouldn't that be noticeable after the finale spot removal step?
So, you should tell Adobe this, not me. This is a forum for users (like me) to help other users (like you).
I know. I just wanted to emphasize why switching to PS wouldn't be the perfect solution for me (even if I'm considering it).
Thanks so far!

Since upgrading to OSX Yosemite my PSE12 freezes when using the clone tool. How do I fix ?

I am looking at a way to fix this freeze as it has completely stopped my workflow which includes patching for each and every one of my 360 degree panoramas. Read: "This is the main reason I purchased PSE12" How can I fix this ? If not does reinstalling help, and if so, where do I go to download the free version without having to repurchase the products since I already have the serial number ? Thanks

Please visit the following link for a possible solution: Photoshop Elements doesn't respond when you use editing tools in Mac OS X 10.10

When using the gradient tool to move a gradient why does the do not symbol show up beside the cross that usually rotates it and how do I get rid of it?

I've tried restarting the tool and the program and it did not work. Here is an example of the do not symbol: Warning, stop and DO NOT symbol | PSDGraphics

You have not provided any system info or details about your document structure, so nobody can know. their could simply be another element or a specific appearance setting preventing this or you have an issue with your input device. Similar behavior has been reported for some Wacom tablets for instance.
Mylenium

Crash or freeze when using Spot Removal

I am having problem with my lightroom 4.2, when I try to use the clone tool my computer crash or keep not responding can anyone help to understand what may be happening ?
Message title was edited by: Brett N

yes it is Windows 7
Date: Sat, 27 Oct 2012 14:46:54 -0600
From: [email protected]
To: [email protected]
Subject: Crash or freeze when using Spot Removal
    Re: Crash or freeze when using Spot Removal
    created by Geoff the kiwi in Photoshop Lightroom - View the full discussion
Is that Windows 7.You can look in the Help Menu in the Menu bar for Lightroom and under System Info you will find what is being asked for.
     Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/4805402#4805402
     Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4805402#4805402
     To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4805402#4805402. In the Actions box on the right, click the Stop Email Notifications link.
     Start a new discussion in Photoshop Lightroom by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

Windows 8 freezing when using Firefox

When I'm using Firefox or Chrome browsers the whole entire PC is freezing.
Already posted my issue on the Microsoft Community forum, where you can read the details and the troubleshooting steps I tried:
http://answers.microsoft.com/en-us/windows/forum/windows_8-networking/windows-8-freezing-when-using-chrome-or-firefox/d6bad301-6c55-4469-96cb-0ec3d43e1113
Also I found another post here on the Mozilla forum, who had the same issue and he did not seem to solve it either: https://support.mozilla.org/en-US/questions/975278?esab=a&as=aaq
Please help me to fix this annoying issue! Thx!

Well, the MS site was a bust, wasn't it?
it would help to know how Firefox is configured.
Can you send me your troubleshooting information from the Firefox installation that's having issues? This is a good part in troubleshooting.
*Navigate to <code>about:support</code> via Address Bar
*Click the button that says <code>Copy text to clipboard</code>
*Now, go back to your forum post and click inside the reply box. Press Ctrl+V to paste all the information you copied into the forum post.
Firefox has hardware acceleration set to "on" by default, but it's still young, which means some video cards or drivers might have problems with it. You can try to disable hardware acceleration to see if that alleviates your problems.
You might need to restart Firefox in order for this to take effect, so save all work first (e.g., mail you are composing, online documents you're editing, etc.).
Then perform these steps for Firefox version 29.0 and above:
*Click the menu button [[Image:New Fx Menu]] and select Options for Windows or Preferences on Mac or Linux. For Firefox 28.0 and previous versions, click the orange Firefox button at the top left, then select the "Options" button, or, if there is no Firefox button at the top, go to Tools > Options.
*In the Firefox options window, click the ''Advanced'' tab, then select "General".
*In the settings list, you should find the ''Use hardware acceleration when available'' checkbox. Uncheck this checkbox.
*Now, restart Firefox and see if the problems persist.
Additionally, please check for updates for your graphics driver by following the steps mentioned in the following Knowledge base articles:
* [[Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems]]
* [[Upgrade your graphics drivers to use hardware acceleration and WebGL]]
Note that if this issue happens in both Chrome and Firefox that it may be a system issue and not a Firefox related issue,
Do a malware check with some malware scanning programs on the Windows computer. 
Please scan with all programs because each program detects different malware. 
All these programs have free versions.
Make sure that you update each program to get the latest version of their databases before doing a scan.
*Malwarebytes' Anti-Malware: http://www.malwarebytes.org/mbam.php
*AdwCleaner: http://www.bleepingcomputer.com/download/adwcleaner/ http://www.softpedia.com/get/Antivirus/Removal-Tools/AdwCleaner.shtml
*SuperAntispyware: http://www.superantispyware.com/
*Microsoft Safety Scanner: http://www.microsoft.com/security/scanner/en-us/default.aspx
*Windows Defender: Home Page: http://www.microsoft.com/windows/products/winfamily/defender/default.mspx
*Spybot Search & Destroy: http://www.safer-networking.org/en/index.html
*Kasperky Free Security Scan: http://www.kaspersky.com/security-scan
You can also do a check for a rootkit infection with TDSSKiller.
*Anti-rootkit utility TDSSKiller: http://support.kaspersky.com/5350?el=88446
See also:
*"Spyware on Windows": http://kb.mozillazine.org/Popups_not_blocked

Test runner freezing when used with Dynamics CRM (and other apps) - Both applications freeze and never come back...

We are trying to use test runner with dynamics CRM.
MS Dynamics CRM will freeze and will not respond (even after 10 - 15 minutes). When this happens, the test manager will either freeze or a message will apear saying "waiting for application under test".
We are not recording action recordings...This makes using test manager impossible. It happens consistently, starting with slowing the PC down (mouse moving slowly, slow to load in new screens, drop downs etc) eventually leading to the app freezing.
Tried on windows xp, windows 7 etc on various specs of pcs.

I am experiencing this same issue with
Test runner freezing when used with Dynamics CRM. I notice this was first posted in June of 2010 and so far no
resolution? I was wondering if it could be related to memory issues? Do you have any troubleshooting ideas? The
issue for me seems to be sporadic and I can't
reproduce it every time.
The message I get is "waiting on application under test".
DLM

IMac 10.6.2 freeze when using iSight

Hello
i have Problems - after i upgrade to 10.6.0 from 10.5... everything was ok .
Then i installed 10.6.1 - still not big problems sometimes hang up - only power off helped .
Since i use 10.6.2 - System freeze when using iSight , ini Chat or Skype after 20 sec.
I tried to go back to 10.6.1 - freeze after 20min .
With 10.6.0 so far no freeze .
I need help .

TnT Sweden wrote:
Hello , once again
i tried these steps with reset , .... did not work .
Also in another account .
So i think i will try to make a clean Installation .
As i am "new" into Mac - what will be the best way .
I had Leopard from the beginning - now bought Snow Leopard .I have Time Capsule for Backup.
My questions - with what System CD i should start to make the clean install ?
10.5 or 10.6 ?
And How ?
What Data will be lost - or is all backup with Time Machine like Photos ,......
Thanks in advance -
If you follow your plan, you will learn a lot and not be nearly so "new" to Mac. Here are my responses to your latest questions/statements:
So i think i will try to make a clean Installation .
In our jargon, a "clean" install means that you will erase your disk and individually reinstall your system and applications, and then restore your data files. This method is very thorough and will give you a pristine system, but it requires considerably more of your time and effort than other methods that may correct your problems.
Easier alternatives are available for your consideration. Before you undertake a system reinstall, read the rest of this post and then study this document and the links in the document that are applicable to your problem and plans:
http://support.apple.com/kb/TS1388
If you decide to reinstall your system, carefully consider your installation options:
http://support.apple.com/kb/HT1545 (also applies to OS 10.6)
As i am "new" into Mac - what will be the best way .
"Best" can mean different things to different people. For example:
• The method explained in the User Guide (manual) that came with your Mac is the easiest way.
• The "Erase and Install" option from http://support.apple.com/kb/HT1545 is quicker to reinstall, but requires more work for apps and data after the OS is installed.
• Archive and Install with the "Preserve user and network settings" option eliminates the need for reinstalling apps and reconfiguring network and other user settings by "preserving" these things during the OS reinstall. Unfortunately, it sometimes also preserves the problem that is causing your difficulty.
• Secure erase before installing OS assures that NOTHING unwanted remains on your disk to cause problems after the reinstall. One pass of writing Zeros is sufficient for your purpose. Note that secure erase will take hours, depending on the size of your disk. The help article below applies to your 10.5&6 as well as the 10.4 it states,:
http://docs.info.apple.com/article.html?path=DiskUtility/10.5/en/duh1011.html
Perhaps easiest of all (as least for Time Machine users) is to use your Mac's Leopard Install DVD and your Time Machine backup to "Restore" your system to a configuration dated BEFORE you did the update that has caused your problems. This method will get you working quickly, but it will not help you use Snow Leopard. If you have not already figured out how to do this "Restore," see:
http://support.apple.com/kb/HT1553
The section entitled " Using Disk Utility" will help you use your Time Machine backup to take your entire system back to when Leopard was working. After it works again, either stay with Leopard, or uninstall or update whatever software is causing your Snow Leopard conflict before again updating to Snow Leopard.
My questions - with what System CD i should start to make the clean install ? 10.5 or 10.6 ?
Use Leopard Install CD if you want to backup to Leopard.
Only use Snow Leopard if you want to try a fresh install of SL to see if you can get it working.
And How ?
Depending on your needs and whether you bought your Mac and SL update locally, and especially if your time is valuable to you, the best way may be to contact your retailer for an appointment so he can either help you or fix your problem for you. If you can use this as a training exercise, you will find it easier to do than to read and write about, and you can ask questions during the process. If you retailer does not consider proper installation of the SL software you bought from him to be part of his service, and if he offers "One to One", you may find it well worth your time and its cost:
http://www.apple.com/retail/onetoone/
If you have plenty of time, or if you merely like doing things for yourself, follow the instructions for the Disk you are using (or the instructions in the links I cite above if you want to try one of those methods.) Remember, you can try an easy/quick way first in case it works without all the manual effort on your part. If that fails to correct your problem, you are only out your time. You can try the next easiest way, and keep trying increasingly complex methods until you find the one that works for you.
What Data will be lost - or is all backup with Time Machine like Photos ,......
This answer varies depending on which method you use to restore your system or reinstall your OS:
• NOTHING IS LOST when you Archive & Install
(if you "preserve user and network settings" before installing)
• EVERYTHING IS LOST when you secure erase.
• Other methods may keep data but lose application or user configuration settings.
(1) I use SL on two Macs and it work GREAT on both. I WANT to use SL because I like it MUCH better than Leopard.&ensp:You did not ask this, but here is how I would proceed to get SL working:
♦ Unless you already have it, I would make another, separate, backup of all important data in addition to the one you already have in Time Machine. One backup is not enough for me. In addition to your music, photos, and other data files, consider items like those listed here:
http://support.apple.com/kb/HT2980
♦ THEN, I would securely erase the startup disk and follow the instructions that came with the SL DVD to install SL.
♦ Immediately after the restart that completes the install, I would use Mac's Disk Utility to repair permissions.
♦ Then configure your internet connection, and download and install the Mac OS X v10.6.2 Update (Combo):
http://support.apple.com/kb/DL959
♦ Immediately after the restart that completes the Combo Update, repair permissions again.
♦ Once you have reinstalled SL, use  > Software Update... to update any other Apple software as needed. I repair permissions before and after any installer than asks me to enter my Administrator Password.
♦ Now you can test your iMac using http://support.apple.com/kb/HT2090 to verify that the problem is resolved. If your problem persists at this point, see your Apple Authorized Service Provider for professional help.
♦ You can restore your data files either now or after reinstalling third-party items.
♦ Now, you can reinstall necessary third-party software. Install only one item at a time and test thoroughly before adding another so you can tell if one of them is causing a problem.
(2) If you would rather retreat to Leopard and not bother trying to fix SL on your Mac, the easiest fix will be to restore your Leopard system from Time Machine. You can then restore any data newer than your last working Leopard system from your backups.
EZ Jim
Mac Pro Quad Core (Early 2009) 2.93Ghz w/Mac OS X (10.6.2) MacBook Pro (13 inch, Mid 2009) 2.26GHz (10.6.2)
LED Cinema Display G4 PowerBook 1.67GHz (10.4.11) iBookSE 366MHz (10.3.9) External iSight

Can you merge two user accounts on macbook? my wife has created a user on her new macbook , then inadvertently created a second one when using the migration tool. 1st ac has her office 365 install, yet 2nd has her itunes database, docs and contacts.

Can you merge two user accounts on a macbook? my wife has created a new user on her new macbook air then, inadvertently, created a second one when using the migration tool. 1st a/c has her office 365 install, while 2nd has her itunes database, docs and contacts. What is the best way forward to get everything into the one account? Not sure if the office 365 will allow another installation into the second account, otherwise would just do that and delete the first, if that is possible?

There is no merge but you can move data from one account to another via the Shared folder. Data is copied from Shared. Watch your free space when copying. These are large files. Do one at a time if you are on a small drive. After making copy, delete from other users before you start next copy.
Office365 installs in the main Applications folder and is available for all users on the computer. Activation is tied to the drive not the User.

After i updated to 10.7.5 my mac keeps freezing when using Safari

After i updated to 10.7.5 my mac keeps freezing when using Safari, I've to restart it everytime. What's the problem with 10.7.5? Is this a known problem? How can I fix it?

Go Here > http://support.apple.com/kb/DL1582 and download and Install the Combo Update.
It is Safe to install over existing.
After the Successul Install be sure to Restart your computer.

Lightroom 2.1 freezes when using new Gradient tool. (Mac 10.5 Leopard)

Similar Messages

Maybe you are looking for