Dual Monitors Photoshop CS4
Here is our setup...
Dell Tower with 2 monitors connected, desktop extended.
What I am wanting to do is have just the image that is being worked on in the right monitor and the image and all the tools on the left monitor. Now I know that you can open a second window for an image but its only for that image, and we work on many images. The right monitor is what the clients see which is also projected for them, left monitor is only seen by us. Is it possible to set this up as a workspace to have the images open up each time in both windows? Or it would even be okay to have them just show up on the right monitor and then have all the tools on the left. Thanks for the help!
Windows XP SP3
Photoshop CS4
Steven Morris
Chetsy Photography
Have you tried to turn "Open Documents as Tabs" off in preferences and then drag out all of photoshop as you would like it to be, and then save the workspace and close photoshop then re-open it and see if everything stays the same? I do a similar thing with premier pro but it doesnt remeber what things are supposed to be on what monitor for some reason, but opens everything properly other than that. Flash would probably be a better example because it has a custom user interface like photoshop. I tried to set that type of viewing up in flash and it seemed to really confuse it and the stage didn't display at all anywhere after closing and re-opening, causing me to have to re-set the workspace. So in short, this may not work but there is always a chance as they are seperate programs....
Similar Messages
-
Using dual monitors with CS4... image opens on wrong one
Has anyone else had this issue with Photoshop CS4? I keep all my panels on the right monitor and work on the left one... normally if I drag my image to the left and save/close it, all future image windows open on that side. Not so with CS4 - it always opens new images underneath my panels, which is a pain.
I looked on another forum and saw one person with this issue, and nobody could help... the conclusion was that it's a bug. Anyone have any ideas? Thanks.There is another work-around.
In the Window Menu, check: Application Frame. Drag the frameover to the second monitor and park it as high up as it will go. When you open files, they will appear on the second monitor, over the Application Frame....which can be minimized to an almost reasonable degree. I've been doing this ever since Adobe decided to change the long standing behavior of opening files on the monitor where you last saved them. It's not perfect but it at least keeps the workflow running the way you are used to. -
Dual monitor color issue - oversaturated image in CS4
Hi, I wonder if you can help. I found people having similar issues, but never seen an actual answer, so your input would be greatly appreciated.
My set-up:
MacBook Pro Dual Core intel based 15.4 2.6GHz running OS X 10.5.6 - also my primary display
HP LP2475- secondary display
CS4
Both monitors were calibrated using X-rite Eye-one LT (each with a separate profile)
I've tried calibrating each monitor 3 times and still get the proble,
My problem:
Running in dual monitor mode in bridge or safari/firefox- no problems at all: almost consistent colour between both monitors.
When I open the images in Photoshop CS4, they look fine on my MacBook screen, but when I drag them over to the HP the color is grossly oversaturated - especially in the red. What am I doing wrong? (in fact on the HP monitor, the color looks perfect in bridge but super insanely saturated in CS4)
Does anyone have a clue on how I can fix this?
Thanks!You say your running 10.5.6? Why haven't you updated to 10.5.8?
FWIW, I never had color issues under 10.5.X, however I have since upgrade to 10.6.
See the thread I started in which Adobe responded:
http://forums.adobe.com/thread/483359 -
Bug - Color Management Photoshop 11 and OS X 10.6 Dual Monitors
I need to know if it's just me, or others are seeing this.
Color management doesn't seem to work properly on dual monitors (MBP + Dell 2408) with Photoshop 11/CS4 and 10.6.
Each of my monitors is independently calibrated and all other apps work fine. For reference Lightroom 2.4/Preview 5.0/FireFox 3.5.2 all render properly across both monitors. Under 10.5 Preview 4.X did not render properly across two monitors, I was so happy in 10.6 it finally did, but PS is WAY more important so I'm kinda bummed.
Anyway, this seems to only happen on the 2nd monitor. If I move the menu bar (Prefs/Displays/Arrangement) to the external monitor making it primary monitor then it works for that monitor, but no longer for the laptop display. Photoshop render images on the 2nd monitor way washed out, but normally on the primary.
Photoshop 11.0.1 worked fine for me on dual monitors under 10.5.So if you've read the links above regarding the "default monitor" issue, people have suggested that a potential workaround is to go to System Preferences>Displays>Arrangement>drag the menu bar from the first diplay to the second
Essentially you make your secondary monitor the default display.
For me what this does to PS is that it now displays the matching colors to Lr in the secondary display (which is now the default display with the menu bar at the top), BUT! when I drag the PS window back into my MacBook display it appears OVERLY saturated...
Strangely Lr appears the same in both windows, AND MORE IMPORTANTLY with the same colors, saturation, brightness, just as it did before I made my Dell 2405FPW the default display. Basically, Lr hasn't shifted in color from display to display or even from display to display after making the secondary monitor my new default display. It has retained the same integrity of colors through all these changes.
Which begs the question, if Lr can't handle dual displays and always uses the color profile of the display it begins in (starts running in), then why does it never shift in color and still look exactly the same after I've made my Dell 2405FPW my primary display?
And actually, if you look really really carefully, Lr DOES produce a color shift between displays as you drag it from one screen to the next. It's extremely fast and happens pretty much as you get 0.5 to 1 inch of the window into the secondary display. It's subtle on my monitor too, which leads me to believe that it performs this color correction properly, quickly, and seamlessly.
What if, my Photoshop 10.0 (old version of CS3) is not registering and understanding the secondary display's color profile correctly? What if it really is PS's fault because everything else looks right? Maybe the issue I'm having is different from what others are experiencing, after all we're in 10.6 now and most of these issues were reported in 10.4 and 10.5? I should probably upgrade my PS CS3 and see what happens?
jb, what version of PS do you have? -
Odd dual monitor behavior in Photoshop CC 2014 on Mavericks
I'm seeing some strange issues with a dual monitor setup (monitor 1 is MacBook Pro screen, monitor 2 is an external monitor) in Photoshop CC 2014. I have images open on both screens. If I use the eyedropper to try to pick a color from an inactive image window on one screen, it won't pick up the color unless I click on the image to make it the active image. I don't remember this behavior on dual monitors before.
I'm also seeing that if I switch from another application back to Photoshop and start painting or erasing, nothing happens in the active window. I have to re-switch applications and try again. Sometimes that works, other times it doesn't.
On another occasion, I was working on one monitor. When I returned to the main monitor and tried to access an item in the Edit menu, all of the menus were empty and white.
I can't identify if this is a Mac OS issue or an Adobe issue. I'm wondering if other people have been experiencing this behavior and if so, how to correct it.
Thanks.Could be. I tried restarting, closing and reopening Photoshop. I just noticed this today, and I've been using CC 2014 since it came out. I'm using it on a relatively new iMac, but I don't think it has happened before, though I could be wrong. It's not the end of the world, but it is an annoyance.
Thanks. -
Does Photoshop CC support dual monitors
I just got off a chat with PS CC support. Since the latest update I have to click several times on photos edited in Camera Raw before they open in PS. The support person tells me that Adobe does not recommend the use of dual monitors. I have been using dual monitors for over 5 years, my computer has plenty of horsepower and every photographer or designer I know uses at least two monitors and sometimes more. It seems ridiculoyus to me that Adobe would say this. Has anyone else run into this concern? Thanx
Jim Cummings.Jim, can you correlate the delay with anything other than Photoshop/Bridge? What drive is the Bridge cache saving to? What drive is Photoshop's primary scratch space assigned to? I'm wondering if those drives are needing to wake up from sleep mode.
If this is happening with previously processed RAW files, could it be to do with their Sidecar files? Do virgin RAW files open OK? You could try converting to DNG perhaps. John Nack blogged about saving a ton of drive space converting all his RAW files to DNG a few days ago. Whoops! I just checked and it was to do with Lightroom
http://jnack.com/blog/2014/06/21/i-just-saved-a-gig-of-hd-space-in-90-seconds/
What's you internet connection like, and are you using Sync Settings? Have you installed any new fonts?
Jeff Tranberry has an excellent trouble shooting step by step guide at:
Photoshop: Basic Troubleshooting steps to fix most issues -
Mac Pro, Leopard 10.5.2, Photoshop CS3, 8800GT and Dual Monitors - Crashing
Hi, I received my Mac Pro (with Nvidia 8800GT) earlier this week and set it up with my dual monitors. I soon discovered that Photoshop CS3 crashes when scrolling a 'zoomed in' image with dual monitors. Photoshop is setup so that all palettes are on the smaller samsung monitor and the main image window I'm working on is on the 23" cinema display.
I've updated both the OS and CS3 but cannot solve the problem unless I switch to a single view setup, ie, drag all the palettes over to the larger monitor so that photoshop is no longer dual monitor. Then it works fine. Although it's a workaround, it's not an ideal situation. Has anyone else found this to be an issue? Have you found a solution?
I've also re-installed Photoshop, visited a genius bar and changed mice!
Thanks, any help would be appreciated.
-NMy Mac Pro had been running 3 Dell monitors on two NVIDIA GeForce 7300 GT cards for months, and with the (I think) Safari update all of a sudden the Mac freezes, 1 monitor displays garbledy gook, and the other is blank with a blinking power light. That is, until yesterday when the power light refused to come on. So I says to myself, "Self, how about testing them on my iBook?" The 1704FPT will not power on, plugged in to a computer or not. The 1707FP shakes like crazy when starting up on the iBook, then settles in and seems to work. Meanwhile, the SP2008WFP is working alone on the Mac Pro, but not totally trouble-free. What the heck is going on?
-
Dual monitors in photoshop elements 11
how can i use dual monitors in photoshop elements 11 in photoshop elements 9 i can simply drag the open file over to the other monitor
Operating system? and how are you opening it? From a shortcut, from the welcome screen, from the organizer, from the program/application file itself?
-
Photoshop CS5 for Windows not working on dual monitor setup
If I try to open Photoshop CS5 while my second monitor is plugged into my laptop (via VGA cable), it loads normally, but won't display any opened images. I get a gray background and nothing else. (see screenshot here: http://screencast.com/t/f1bHcM3E )
(I can even see the tiny image preview in the navigator, but not the image itself.)
However, t'll work just fine if I open Photoshop with the second monitor disconnected and THEN plug it in, so it's not a problem with the dual monitors in general...just when first opening it. It's annoying because, if I'm working on a project and realize I have to make a quick image tweak in Photoshop, I have to unplug the monitor and then rearrange all my windows after Photoshop's done loading and I can plug it back in.
Does anyone have any idea what's up with this? I can't seem to find any information online that specifically mentions this issue. For reference, I'm using Windows 7 on a Lenovo laptop.
Thanks!Oh, that's possible. I went and read the detailed specs for my computer and it seems like it has both Intel and NVIDIA. Could that be it? (Computer hardware issues are not my area of expertise.)
-
Photoshop cs4 and multiple monitors
When i save a document as a jpg on one monitor and then drag the photoshop window to the other monitor and save it the same way, they turn out differently! Whats going on?
JohnVega
"On the Mac, the Application frame groups all the workspace elements in a single, integrated window that lets you treat the application as a single unit. When you move or resize the Application frame or any of its elements, all the elements within it respond to each other so none overlap. Panels dont disappear when you switch applications or when you accidentally click out of the application. If you work with two or more applications, you can position each application side by side on the screen or on multiple monitors. If you prefer the traditional, free-form user interface of the Mac, you can turn off the Application frame. In Adobe Illustrator®, for example, select Window > Application Frame to toggle it on or off." - Adobe Help "Using Photoshop CS4"
Once you have done that, move the whole block of the Application frame to the Display Tablet. You can then toggle between the monitor 1 and tablet monitor by switching on/off Application frame.. -
Photoshop CS4 Brushes not Anti Aliasing properly
I've just set up CS4 and my brushes are not anti aliasing properly. There are no soft edges on any of them. I'm able to get a pressure sensitive opacity change on the stroke but the edges are all pixelated.
Here is an image (this is a soft brush. notice none of the feathering/anti aliasing is there):
http://craji.com/images/adobeproblem.jpg
I've updated the newest gpu drivers for my Nvidia 8800 GTS.
I'm running XP SP3 with dual monitors. An Apple 30" and a Cintiq 21"
I've tried placing the main photoshop window on both monitors (one at a time) to test if that was causing it and i've had no luck.
All of the options in my GPU Enabled are currently unchecked (since they were giving me lag issues on my brush stroke when they were checked).
Any help (even linking me to something similar in this forum) is greatly appreciated.
Cheers-Definitely not file dependent. I'll open a photo in sRGB 8bit, or create a new document with any settings from cmyk/rgb/bw 8/16 etc.
I'm wondering if it has something to do with my Nvidia Display Property utility. I use it to gamma up my secondary monitor (cintiq). Although disabling that utility didn't resolve it..
I'll try uninstalling and reinstalling tonight if no one is having similar problems. Maybe that will fix it. -
DUAL MONITOR BUG: One Picture – One Monitor – Different Colors!
There have been several threads discussing that Photoshop CS4 and OS 10.6. show wrong colors in dual monitor setups.
The first one to prove this with a screen capture was jb510-LJ0JJQ in August 2009: http://forums.adobe.com/message/2207312#2207312
Eight months and three OS updates later the problem is still there and makes professional work with more than one monitor a nuisance.
Here's another actual example: A picture and its 100% identical copy showing different colors on one screen!
Here's how to repeat it – try this at home ;-)
1) In the finder make a copy of a rgb picture.
2) Open one of the two identical pics in photoshop.
3) Drag it to the other monitor.
When releasing the mouse button you may see the bug already: the colors will "switch".
4) To verify this go to system presets - monitors - and change the primary monitor (by dragging the menu bar to the other)
5) Now open the identical copy you made in step 1) and see the difference!
Here's a synopsis of suggested workarounds:
1) disable open GL (which seem to makes no difference on my setup)
2) click "desaturate monitor colors" but set desaturation to 0 (which prevents visual switching in step 3) (only if openGL is ON) but also leads to a wrong display in step 4+5
3) make the hardware calibrated monitor your default monitor and strictly avoid changes or dragging pics to the other monitor (which seems to be the only reliable method)
4) some guys even force both monitors to use the profile of their hardware-calibrated monitor (using color sync) to make sure they see what they should see on at least that one monitor. What a stone-age workaround for the the world's leading imaging program!
Considering that reliable colors in professional (=multi monitor) settings should be the most basic function of photoshop this mayor malfunction should be solved with CS5! Otherwise we might have to live with it for some more years...
Have Adobe and Apple realized this bug and on their agenda? Will it be gone with OS 10.6.3? Can anyone explain the reasons for this bad bug? Is there a "officially" recommended workaround?
Thanks, regards,
EricThere have been several threads dealing with this malfunction. But most faded out in silence or acceptance of the workarounds.
http://forums.adobe.com/message/2207312#2207312
http://forums.adobe.com/thread/521483
http://forums.adobe.com/message/2272192#2272192
http://forums.adobe.com/thread/311761?start=0&tstart=0
http://forums.adobe.com/thread/618927?tstart=60
http://forums.adobe.com/thread/603992?tstart=90
http://www.wetcanvas.com/forums/showthread.php?t=552977
http://www.hilfdirselbst.ch/gforum/gforum.cgi?post=368889?search_string=zwei%20monitor#368 889
But man, this is no minor bug! Consistent colors are the by far most important basic function of photoshop. If you cannot rely on the colors in photoshop you can as well use "Preview" and "Word" for print production ;-)
Carson, how did Apple react to your complaint? What do you mean with "they don't get it". Do they not see it? Or can't they get it right?
Shall we open a thread at apple forums to point out that it's not the problem of a single user? -
Monitor Profile incorrect on Dual Monitor Setup
Hello,
I've searched the forums and I can't find an answer to my problem. I've read about dual monitor setups in Windows and how to set the defaults and whatnot, but it doesn't seem to fix my problem.
I am running on an nVidia GeForce 8600M GT, Windows 7 x64, Photoshop CS4 x64. I calibrated my main display (Dell Vostro 1700) as well as the attached monitor (ASUS VK246H) using Datacolor Spyder3Elite. Both monitor profiles seem to load just fine. I've also went into Windows' color manager and set the system defaults for each monitor respectively. The problem I'm having is that if I were to load Photoshop on the 2nd monitor, Photoshop only uses the main display's color profile (Vostro 1700) and not the ASUS VK246H profile. What could be going wrong?
Just to clarify, what I mean by "loading PS on the 2nd monitor" is that when I execute Photoshop.exe, the splash screen and main window shows up on the 2nd monitor, not the main monitor (which is what I want).function(){return A.apply(null,[this].concat($A(arguments)))}
Chris Cox wrote:
What if the image is in between two monitors?
The piece on each display is corrected for the display it is on.
Is it supposed to work that way? Because it doesn't. Not with Photoshop CS5 x64 at least.
As a test I intentionally misconfigured the profile for my Monitor #1 (left) so that it's REALLY OBVIOUS which profile is being used. When set this way, on Monitor #1 red colors will appear pale orange.
An open document, floating in a window:
If COMPLETELY displayed on Monitor #1, Photoshop will use the Monitor #1 profile.
If even 1 pixel of the edge of the image is moved onto Monitor #2, it will use the Monitor #2 profile on the entire image.
See for yourself:
-Noel -
Why does Photoshop CS4 keep crashing?! (Mac OS)
I use Photoshop often, daily even. I upgraded to CS4 at the beginning of this year and have a CONSTANT and very IRRITATING problem. It keeps crashing, for no apparent reason. It will crash during all kinds of "tasks". Saving, opening an image from RAW, using the liquify tool, using the clone tool, running an action and any number of others tasks cause a crash in Photoshop CS4.
I work relatively fast, as I use Photoshop on a daily basis. This is how it will happen...
I'll be working on an image and I "command S" to save. There will be a slight delay of about 2-4 seconds and then Photoshop will crash and I will get a pop-up screen to submit a crash report. I have submitted literally hundreds, if not thousands of these. Then, Photoshop sits idle for a few minutes as if it is locked up, unable to "Relaunch". So, I then usually have to "Force Quit" Photoshop, yet, it will not immediatly quit. It takes another couple of minutes to do so before I am able to begin working again. This process happens, on average, a couple of times per hour, if not more.
Luckily, I have "trained" myself to save after almost ever thing I do. But, I inevitable loose something as it happens just after a "task" or during a "save". (It happens during a save frequently.) Plus, I'm loosing valuable time waiting on it to Relaunch, and figuring out where I'm at on the image all over again.
Needless to say, I'm beyond frustrated, to say the least.
There is something else that doesn't make sense. My business partner, who also has a new IMac (not the VERY newest model that just came out but the one just prior to that...It was purchased in December 08 as well) and also runs CS4 does not have this crashing problem! At all! Not once.
Here's the difference in our systems...He purchased the 24" model, while I purchased the 20". And, this is where I actually think the problem may lie...I am running dual monitors, while he does not.
I've tried to trouble-shoot this problem, since he does not have the problem, while I do. I did "About this Mac" on both our machines to see if there were any obvious differences, besides running dual monitors. What I found under HARDWARD were only two minor differences. His processor speed is 2.8 while mine is 2.66 GHz. and the SMC Version of his machine is 1.3f1, while mine is 1.29f1. There were no differences in the GRAPHICS/DISPLAYS section either, beyond my having a second display.
Both his and my graphics/displays are as follows:
ATI Radeon HD 2600 Pro:
Chipset Model: ATI Radeon HD 2600 Pro
Type: Display
Bus: PCIe
PCIe Lane Width: x16
VRAM (Total): 256 MB
Vendor: ATI (0x1002)
Device ID: 0x9583
Revision ID: 0x0000
ROM Revision: 113-B2250L-259
EFI Driver Version: 01.00.259
Displays:
iMac:
Resolution: 1280 x 800
Depth: 32-bit Color
Core Image: Hardware Accelerated
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Built-In: Yes
Below is the information regarding my second display.
LaCie 324:
Resolution: 1920 x 1200 @ 60 Hz
Depth: 32-bit Color
Core Image: Hardware Accelerated
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
Television: Yes
As you can see, my second display is a Lacie 324. It is rather new, I purchased it in November or December 08 as well as my IMac. I have the Lacie set as my main display.
When I have Googled this Photoshop CS4 crash problem, I have come across some mention of the GPU Settings and Enable OpenGL Drawing. I have to admit, I really don't understand this. Should OpenGL Drawing be on or off??? I turned OpenGL Drawing off some time ago because I had a problem with calibrating my Lacie monitor. My monitor was showing images skewed toward red, while my prints were coming out with less red. I Googled this problem (at the time I didn't think this was related to the crashing issue) and someone said they were having trouble calibrating their monitor as well and managed to "fix" that by turning "Enable OpenGL Drawing" off. I did that and it did indeed fix the problem with getting my Lacie monitor calibrated. FYI, my business partner also turned off the Enable OpenGL Drawing feature and...again...he has NOT had the problem with Photoshop CS4 crashing. So, since he is not having the problem and I am, I would assume the "Enable OpenGL Drawing" issue that is mentioned on this site, is not the crashing problem, though I could be wrong.
So, I go back to having a second monitor as being the most-likely candidate for causing the Photoshop crashes. I am wondering if the Lacie display is "drawing" the graphics at the speed that differs, or is incompatable, with Photoshop CS4??? This is just a guess from someone who is not all that technically savy. But, again, I'm not sure. I have also looked on the Lacie website for any updates for the Lacie 324. There are none, as far as I can tell.
I am curious if others with and without dual monitors are having these crashes. If so, have you found any resolution? I'm desperate for help so if anyone can shed any light on this issue, it would be most appreciated.
Below, I will put some specs about my machine, in case that is helpful.
Hardware Overview:
Model Name: iMac
Model Identifier: iMac8,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.66 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 6 MB
Memory: 4 GB
Bus Speed: 1.07 GHz
Boot ROM Version: IM81.00C1.B00
SMC Version: 1.29f1
I have the 11.0.1 version of Photoshop CS4.
PLEASE help if you can. Thanks so much!
DGJ [email address deleted by host]Process: Adobe Photoshop CS4 [341]
Path: /Applications/Adobe Photoshop CS4/Adobe Photoshop CS4.app/Contents/MacOS/Adobe Photoshop CS4
Identifier: com.adobe.Photoshop
Version: 11.0.1 (11.0.1x20090216 [20090216.r.522 2009/02/16:17:00:00 cutoff; r branch]) (11.0.1)
Code Type: X86 (Native)
Parent Process: launchd [243]
Date/Time: 2009-05-12 20:39:54.924 -0400
OS Version: Mac OS X 10.5.7 (9J61)
Report Version: 6
Anonymous UUID: 9A059F57-309E-4E59-893D-54D405B7DCE2
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000ffdf4060
Crashed Thread: 0
Thread 0 Crashed:
0 com.apple.HIToolbox 0x9357d4d8 RemoveEventHandler + 48
1 com.apple.HIToolbox 0x9369e122 CCarbonEventHandler::InitCarbonEventHandler(TXNCarbonEventInfo*) + 344
2 com.apple.HIToolbox 0x9369df8e CTextension::StartCarbonEventHandler(OpaqueTXNObject*, TXNCarbonEventInfo*) + 112
3 com.apple.HIToolbox 0x935e52e2 OpaqueTXNObject::InstallCarbonEventHandler(OpaqueWindowPtr*, OpaqueWindowPtr*) + 384
4 com.apple.HIToolbox 0x93691858 OpaqueTXNObject::AttachObjectToWindowRef(OpaqueWindowPtr*, unsigned char) + 388
5 com.apple.HIToolbox 0x936d2430 TXNAttachObjectToWindowRef + 66
6 com.adobe.Photoshop 0x000c3f8e 0x1000 + 798606
7 com.adobe.Photoshop 0x000c69c6 0x1000 + 809414
8 com.adobe.Photoshop 0x000d29dd 0x1000 + 858589
9 com.adobe.Photoshop 0x000d2bab 0x1000 + 859051
10 com.adobe.Photoshop 0x000d2bab 0x1000 + 859051
11 com.adobe.Photoshop 0x000d2bab 0x1000 + 859051
12 com.adobe.Photoshop 0x000d2bab 0x1000 + 859051
13 com.adobe.Photoshop 0x000d2bab 0x1000 + 859051
14 com.adobe.Photoshop 0x000d2bab 0x1000 + 859051
15 com.adobe.Photoshop 0x000d2bab 0x1000 + 859051
16 com.adobe.Photoshop 0x000d2bab 0x1000 + 859051
17 com.adobe.Photoshop 0x002fcbcb 0x1000 + 3128267
18 com.adobe.Photoshop 0x002fd40f 0x1000 + 3130383
19 com.adobe.Photoshop 0x002fd773 0x1000 + 3131251
20 com.adobe.Photoshop 0x000cdcab 0x1000 + 838827
21 com.adobe.Photoshop 0x000d29a2 0x1000 + 858530
22 com.adobe.Photoshop 0x000d2bab 0x1000 + 859051
23 com.adobe.Photoshop 0x000d2bab 0x1000 + 859051
24 com.adobe.Photoshop 0x000d99f5 0x1000 + 887285
25 com.adobe.Photoshop 0x000d2df0 0x1000 + 859632
26 com.adobe.Photoshop 0x000d2df0 0x1000 + 859632
27 com.adobe.Photoshop 0x000d2df0 0x1000 + 859632
28 com.adobe.Photoshop 0x000d2df0 0x1000 + 859632
29 com.adobe.Photoshop 0x000d2df0 0x1000 + 859632
30 com.adobe.Photoshop 0x000d2df0 0x1000 + 859632
31 com.adobe.Photoshop 0x0006e70c 0x1000 + 448268
32 com.adobe.Photoshop 0x000d2df0 0x1000 + 859632
33 com.adobe.Photoshop 0x0006e70c 0x1000 + 448268
34 com.adobe.Photoshop 0x000d2df0 0x1000 + 859632
35 com.adobe.Photoshop 0x000bb51c 0x1000 + 763164
36 com.adobe.Photoshop 0x000d2df0 0x1000 + 859632
37 com.adobe.Photoshop 0x000c9be9 0x1000 + 822249
38 com.adobe.Photoshop 0x0034ca1d 0x1000 + 3455517
39 com.adobe.Photoshop 0x00566ae4 0x1000 + 5659364
40 com.adobe.Photoshop 0x004eb324 0x1000 + 5153572
41 com.adobe.Photoshop 0x004ebc7e 0x1000 + 5155966
42 com.adobe.Photoshop 0x004ebd09 0x1000 + 5156105
43 com.adobe.Photoshop 0x0048cc4a 0x1000 + 4766794
44 com.adobe.Photoshop 0x0048de73 0x1000 + 4771443
45 com.adobe.Photoshop 0x0006b9ed 0x1000 + 436717
46 com.adobe.Photoshop 0x0006a79d 0x1000 + 432029
47 com.adobe.Photoshop 0x00063d65 0x1000 + 404837
48 com.adobe.Photoshop 0x00063ed3 0x1000 + 405203
49 com.adobe.Photoshop 0x0006222f 0x1000 + 397871
50 com.adobe.Photoshop 0x002206aa 0x1000 + 2225834
51 com.adobe.Photoshop 0x00220736 0x1000 + 2225974
52 com.adobe.Photoshop 0x00003912 0x1000 + 10514
53 com.adobe.Photoshop 0x00003839 0x1000 + 10297
Thread 1:
0 libSystem.B.dylib 0x900649c6 kevent + 10
1 libSystem.B.dylib 0x90065155 _pthread_start + 321
2 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 2:
0 libSystem.B.dylib 0x900342ce semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x900662c6 _pthread_cond_wait + 1267
2 libSystem.B.dylib 0x900ab539 pthread_cond_wait + 48
3 com.adobe.amt.services 0x04b69552 AMTConditionLock::LockWhenCondition(int) + 46
4 com.adobe.amt.services 0x04b64995 _AMTThreadedPCDService::PCDThreadWorker(_AMTThreadedPCDService*) + 115
5 com.adobe.amt.services 0x04b695b0 AMTThread::Worker(void*) + 20
6 libSystem.B.dylib 0x90065155 _pthread_start + 321
7 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 3:
0 libSystem.B.dylib 0x9003b46e __semwait_signal + 10
1 libSystem.B.dylib 0x90065dcd pthread_cond_wait$UNIX2003 + 73
2 libGLProgrammability.dylib 0x91afeb32 glvmDoWork + 162
3 libSystem.B.dylib 0x90065155 _pthread_start + 321
4 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 4:
0 libSystem.B.dylib 0x900342da semaphore_timedwait_trap + 10
1 ...ple.CoreServices.CarbonCore 0x96cf047f MPWaitOnSemaphore + 125
2 MultiProcessor Support 0x1e2a3eff 0x1e274000 + 196351
3 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
4 libSystem.B.dylib 0x90065155 _pthread_start + 321
5 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 5:
0 libSystem.B.dylib 0x900342da semaphore_timedwait_trap + 10
1 ...ple.CoreServices.CarbonCore 0x96cf047f MPWaitOnSemaphore + 125
2 MultiProcessor Support 0x1e2a3eff 0x1e274000 + 196351
3 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
4 libSystem.B.dylib 0x90065155 _pthread_start + 321
5 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 6:
0 libSystem.B.dylib 0x900342da semaphore_timedwait_trap + 10
1 ...ple.CoreServices.CarbonCore 0x96cf047f MPWaitOnSemaphore + 125
2 MultiProcessor Support 0x1e2a3eff 0x1e274000 + 196351
3 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
4 libSystem.B.dylib 0x90065155 _pthread_start + 321
5 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 7:
0 libSystem.B.dylib 0x900342da semaphore_timedwait_trap + 10
1 ...ple.CoreServices.CarbonCore 0x96cf047f MPWaitOnSemaphore + 125
2 MultiProcessor Support 0x1e2a3eff 0x1e274000 + 196351
3 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
4 libSystem.B.dylib 0x90065155 _pthread_start + 321
5 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 8:
0 libSystem.B.dylib 0x900342da semaphore_timedwait_trap + 10
1 ...ple.CoreServices.CarbonCore 0x96cf047f MPWaitOnSemaphore + 125
2 MultiProcessor Support 0x1e2a3eff 0x1e274000 + 196351
3 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
4 libSystem.B.dylib 0x90065155 _pthread_start + 321
5 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 9:
0 libSystem.B.dylib 0x900342da semaphore_timedwait_trap + 10
1 ...ple.CoreServices.CarbonCore 0x96cf047f MPWaitOnSemaphore + 125
2 MultiProcessor Support 0x1e2a3eff 0x1e274000 + 196351
3 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
4 libSystem.B.dylib 0x90065155 _pthread_start + 321
5 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 10:
0 libSystem.B.dylib 0x900342da semaphore_timedwait_trap + 10
1 ...ple.CoreServices.CarbonCore 0x96cf047f MPWaitOnSemaphore + 125
2 MultiProcessor Support 0x1e2a3eff 0x1e274000 + 196351
3 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
4 libSystem.B.dylib 0x90065155 _pthread_start + 321
5 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 11:
0 libSystem.B.dylib 0x900342da semaphore_timedwait_trap + 10
1 ...ple.CoreServices.CarbonCore 0x96cf047f MPWaitOnSemaphore + 125
2 MultiProcessor Support 0x1e2a3eff 0x1e274000 + 196351
3 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
4 libSystem.B.dylib 0x90065155 _pthread_start + 321
5 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 12:
0 libSystem.B.dylib 0x900342da semaphore_timedwait_trap + 10
1 ...ple.CoreServices.CarbonCore 0x96cf047f MPWaitOnSemaphore + 125
2 MultiProcessor Support 0x1e2a3eff 0x1e274000 + 196351
3 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
4 libSystem.B.dylib 0x90065155 _pthread_start + 321
5 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 13:
0 libSystem.B.dylib 0x900342da semaphore_timedwait_trap + 10
1 ...ple.CoreServices.CarbonCore 0x96cf047f MPWaitOnSemaphore + 125
2 MultiProcessor Support 0x1e2a3eff 0x1e274000 + 196351
3 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
4 libSystem.B.dylib 0x90065155 _pthread_start + 321
5 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 14:
0 libSystem.B.dylib 0x900342da semaphore_timedwait_trap + 10
1 ...ple.CoreServices.CarbonCore 0x96cf047f MPWaitOnSemaphore + 125
2 MultiProcessor Support 0x1e2a3eff 0x1e274000 + 196351
3 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
4 libSystem.B.dylib 0x90065155 _pthread_start + 321
5 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 15:
0 libSystem.B.dylib 0x900342da semaphore_timedwait_trap + 10
1 ...ple.CoreServices.CarbonCore 0x96cf047f MPWaitOnSemaphore + 125
2 MultiProcessor Support 0x1e2a3eff 0x1e274000 + 196351
3 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
4 libSystem.B.dylib 0x90065155 _pthread_start + 321
5 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 16:
0 libSystem.B.dylib 0x900342da semaphore_timedwait_trap + 10
1 ...ple.CoreServices.CarbonCore 0x96cf047f MPWaitOnSemaphore + 125
2 MultiProcessor Support 0x1e2a3eff 0x1e274000 + 196351
3 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
4 libSystem.B.dylib 0x90065155 _pthread_start + 321
5 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 17:
0 libSystem.B.dylib 0x900342da semaphore_timedwait_trap + 10
1 ...ple.CoreServices.CarbonCore 0x96cf047f MPWaitOnSemaphore + 125
2 MultiProcessor Support 0x1e2a3eff 0x1e274000 + 196351
3 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
4 libSystem.B.dylib 0x90065155 _pthread_start + 321
5 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 18:
0 libSystem.B.dylib 0x900342da semaphore_timedwait_trap + 10
1 ...ple.CoreServices.CarbonCore 0x96cf047f MPWaitOnSemaphore + 125
2 MultiProcessor Support 0x1e2a3eff 0x1e274000 + 196351
3 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
4 libSystem.B.dylib 0x90065155 _pthread_start + 321
5 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 19:
0 libSystem.B.dylib 0x9003b46e __semwait_signal + 10
1 libSystem.B.dylib 0x90065dcd pthread_cond_wait$UNIX2003 + 73
2 ...ple.CoreServices.CarbonCore 0x96cdee83 TSWaitOnCondition + 126
3 ...ple.CoreServices.CarbonCore 0x96cbdd6a TSWaitOnConditionTimedRelative + 202
4 ...ple.CoreServices.CarbonCore 0x96cdeb00 MPWaitOnQueue + 208
5 AdobeACE 0x027c138d 0x2790000 + 201613
6 AdobeACE 0x027c0d85 0x2790000 + 200069
7 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
8 libSystem.B.dylib 0x90065155 _pthread_start + 321
9 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 20:
0 libSystem.B.dylib 0x9003b46e __semwait_signal + 10
1 libSystem.B.dylib 0x90065dcd pthread_cond_wait$UNIX2003 + 73
2 ...ple.CoreServices.CarbonCore 0x96cdee83 TSWaitOnCondition + 126
3 ...ple.CoreServices.CarbonCore 0x96cbdd6a TSWaitOnConditionTimedRelative + 202
4 ...ple.CoreServices.CarbonCore 0x96cdeb00 MPWaitOnQueue + 208
5 AdobeACE 0x027c138d 0x2790000 + 201613
6 AdobeACE 0x027c0d85 0x2790000 + 200069
7 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
8 libSystem.B.dylib 0x90065155 _pthread_start + 321
9 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 21:
0 libSystem.B.dylib 0x9003b46e __semwait_signal + 10
1 libSystem.B.dylib 0x90065dcd pthread_cond_wait$UNIX2003 + 73
2 ...ple.CoreServices.CarbonCore 0x96cdee83 TSWaitOnCondition + 126
3 ...ple.CoreServices.CarbonCore 0x96cbdd6a TSWaitOnConditionTimedRelative + 202
4 ...ple.CoreServices.CarbonCore 0x96cdeb00 MPWaitOnQueue + 208
5 AdobeACE 0x027c138d 0x2790000 + 201613
6 AdobeACE 0x027c0d85 0x2790000 + 200069
7 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
8 libSystem.B.dylib 0x90065155 _pthread_start + 321
9 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 22:
0 libSystem.B.dylib 0x9003b46e __semwait_signal + 10
1 libSystem.B.dylib 0x90065dcd pthread_cond_wait$UNIX2003 + 73
2 ...ple.CoreServices.CarbonCore 0x96cdee83 TSWaitOnCondition + 126
3 ...ple.CoreServices.CarbonCore 0x96cbdd6a TSWaitOnConditionTimedRelative + 202
4 ...ple.CoreServices.CarbonCore 0x96cdeb00 MPWaitOnQueue + 208
5 AdobeACE 0x027c138d 0x2790000 + 201613
6 AdobeACE 0x027c0d85 0x2790000 + 200069
7 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
8 libSystem.B.dylib 0x90065155 _pthread_start + 321
9 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 23:
0 libSystem.B.dylib 0x9003b46e __semwait_signal + 10
1 libSystem.B.dylib 0x90065dcd pthread_cond_wait$UNIX2003 + 73
2 ...ple.CoreServices.CarbonCore 0x96cdee83 TSWaitOnCondition + 126
3 ...ple.CoreServices.CarbonCore 0x96cbdd6a TSWaitOnConditionTimedRelative + 202
4 ...ple.CoreServices.CarbonCore 0x96cdeb00 MPWaitOnQueue + 208
5 AdobeACE 0x027c138d 0x2790000 + 201613
6 AdobeACE 0x027c0d85 0x2790000 + 200069
7 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
8 libSystem.B.dylib 0x90065155 _pthread_start + 321
9 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 24:
0 libSystem.B.dylib 0x9003b46e __semwait_signal + 10
1 libSystem.B.dylib 0x90065dcd pthread_cond_wait$UNIX2003 + 73
2 ...ple.CoreServices.CarbonCore 0x96cdee83 TSWaitOnCondition + 126
3 ...ple.CoreServices.CarbonCore 0x96cbdd6a TSWaitOnConditionTimedRelative + 202
4 ...ple.CoreServices.CarbonCore 0x96cdeb00 MPWaitOnQueue + 208
5 AdobeACE 0x027c138d 0x2790000 + 201613
6 AdobeACE 0x027c0d85 0x2790000 + 200069
7 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
8 libSystem.B.dylib 0x90065155 _pthread_start + 321
9 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 25:
0 libSystem.B.dylib 0x9003b46e __semwait_signal + 10
1 libSystem.B.dylib 0x90065dcd pthread_cond_wait$UNIX2003 + 73
2 ...ple.CoreServices.CarbonCore 0x96cdee83 TSWaitOnCondition + 126
3 ...ple.CoreServices.CarbonCore 0x96cbdd6a TSWaitOnConditionTimedRelative + 202
4 ...ple.CoreServices.CarbonCore 0x96cdeb00 MPWaitOnQueue + 208
5 AdobeACE 0x027c138d 0x2790000 + 201613
6 AdobeACE 0x027c0d85 0x2790000 + 200069
7 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
8 libSystem.B.dylib 0x90065155 _pthread_start + 321
9 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 26:
0 libSystem.B.dylib 0x9003b46e __semwait_signal + 10
1 libSystem.B.dylib 0x90065dcd pthread_cond_wait$UNIX2003 + 73
2 ...ple.CoreServices.CarbonCore 0x96cdee83 TSWaitOnCondition + 126
3 ...ple.CoreServices.CarbonCore 0x96cbdd6a TSWaitOnConditionTimedRelative + 202
4 ...ple.CoreServices.CarbonCore 0x96cdeb00 MPWaitOnQueue + 208
5 AdobeACE 0x027c138d 0x2790000 + 201613
6 AdobeACE 0x027c0d85 0x2790000 + 200069
7 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
8 libSystem.B.dylib 0x90065155 _pthread_start + 321
9 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 27:
0 libSystem.B.dylib 0x9003b46e __semwait_signal + 10
1 libSystem.B.dylib 0x90065dcd pthread_cond_wait$UNIX2003 + 73
2 ...ple.CoreServices.CarbonCore 0x96cdee83 TSWaitOnCondition + 126
3 ...ple.CoreServices.CarbonCore 0x96cbdd6a TSWaitOnConditionTimedRelative + 202
4 ...ple.CoreServices.CarbonCore 0x96cdeb00 MPWaitOnQueue + 208
5 AdobeACE 0x027c138d 0x2790000 + 201613
6 AdobeACE 0x027c0d85 0x2790000 + 200069
7 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
8 libSystem.B.dylib 0x90065155 _pthread_start + 321
9 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 28:
0 libSystem.B.dylib 0x9003b46e __semwait_signal + 10
1 libSystem.B.dylib 0x90065dcd pthread_cond_wait$UNIX2003 + 73
2 ...ple.CoreServices.CarbonCore 0x96cdee83 TSWaitOnCondition + 126
3 ...ple.CoreServices.CarbonCore 0x96cbdd6a TSWaitOnConditionTimedRelative + 202
4 ...ple.CoreServices.CarbonCore 0x96cdeb00 MPWaitOnQueue + 208
5 AdobeACE 0x027c138d 0x2790000 + 201613
6 AdobeACE 0x027c0d85 0x2790000 + 200069
7 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
8 libSystem.B.dylib 0x90065155 _pthread_start + 321
9 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 29:
0 libSystem.B.dylib 0x9003b46e __semwait_signal + 10
1 libSystem.B.dylib 0x90065dcd pthread_cond_wait$UNIX2003 + 73
2 ...ple.CoreServices.CarbonCore 0x96cdee83 TSWaitOnCondition + 126
3 ...ple.CoreServices.CarbonCore 0x96cbdd6a TSWaitOnConditionTimedRelative + 202
4 ...ple.CoreServices.CarbonCore 0x96cdeb00 MPWaitOnQueue + 208
5 AdobeACE 0x027c138d 0x2790000 + 201613
6 AdobeACE 0x027c0d85 0x2790000 + 200069
7 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
8 libSystem.B.dylib 0x90065155 _pthread_start + 321
9 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 30:
0 libSystem.B.dylib 0x9003b46e __semwait_signal + 10
1 libSystem.B.dylib 0x90065dcd pthread_cond_wait$UNIX2003 + 73
2 ...ple.CoreServices.CarbonCore 0x96cdee83 TSWaitOnCondition + 126
3 ...ple.CoreServices.CarbonCore 0x96cbdd6a TSWaitOnConditionTimedRelative + 202
4 ...ple.CoreServices.CarbonCore 0x96cdeb00 MPWaitOnQueue + 208
5 AdobeACE 0x027c138d 0x2790000 + 201613
6 AdobeACE 0x027c0d85 0x2790000 + 200069
7 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
8 libSystem.B.dylib 0x90065155 _pthread_start + 321
9 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 31:
0 libSystem.B.dylib 0x9003b46e __semwait_signal + 10
1 libSystem.B.dylib 0x90065dcd pthread_cond_wait$UNIX2003 + 73
2 ...ple.CoreServices.CarbonCore 0x96cdee83 TSWaitOnCondition + 126
3 ...ple.CoreServices.CarbonCore 0x96cbdd6a TSWaitOnConditionTimedRelative + 202
4 ...ple.CoreServices.CarbonCore 0x96cdeb00 MPWaitOnQueue + 208
5 AdobeACE 0x027c138d 0x2790000 + 201613
6 AdobeACE 0x027c0d85 0x2790000 + 200069
7 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
8 libSystem.B.dylib 0x90065155 _pthread_start + 321
9 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 32:
0 libSystem.B.dylib 0x9003b46e __semwait_signal + 10
1 libSystem.B.dylib 0x90065dcd pthread_cond_wait$UNIX2003 + 73
2 ...ple.CoreServices.CarbonCore 0x96cdee83 TSWaitOnCondition + 126
3 ...ple.CoreServices.CarbonCore 0x96cbdd6a TSWaitOnConditionTimedRelative + 202
4 ...ple.CoreServices.CarbonCore 0x96cdeb00 MPWaitOnQueue + 208
5 AdobeACE 0x027c138d 0x2790000 + 201613
6 AdobeACE 0x027c0d85 0x2790000 + 200069
7 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
8 libSystem.B.dylib 0x90065155 _pthread_start + 321
9 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 33:
0 libSystem.B.dylib 0x9003b46e __semwait_signal + 10
1 libSystem.B.dylib 0x90065dcd pthread_cond_wait$UNIX2003 + 73
2 ...ple.CoreServices.CarbonCore 0x96cdee83 TSWaitOnCondition + 126
3 ...ple.CoreServices.CarbonCore 0x96cbdd6a TSWaitOnConditionTimedRelative + 202
4 ...ple.CoreServices.CarbonCore 0x96cdeb00 MPWaitOnQueue + 208
5 AdobeACE 0x027c138d 0x2790000 + 201613
6 AdobeACE 0x027c0d85 0x2790000 + 200069
7 ...ple.CoreServices.CarbonCore 0x96cdd057 PrivateMPEntryPoint + 56
8 libSystem.B.dylib 0x90065155 _pthread_start + 321
9 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 34:
0 libSystem.B.dylib 0x900343a6 mach_wait_until + 10
1 libSystem.B.dylib 0x900ab3ad nanosleep + 314
2 com.adobe.PSAutomate 0x23cc6755 ScObjects::Thread::sleep(unsigned int) + 143
3 com.adobe.PSAutomate 0x23cc67b5 ScObjects::Thread::wait(unsigned int) + 23
4 com.adobe.PSAutomate 0x23cb7502 ScObjects::BridgeTalkThread::run() + 332
5 com.adobe.PSAutomate 0x23cc6a77 ScObjects::Thread::go(void*) + 239
6 libSystem.B.dylib 0x90065155 _pthread_start + 321
7 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 35:
0 libSystem.B.dylib 0x900342ce semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x900662c6 _pthread_cond_wait + 1267
2 libSystem.B.dylib 0x900ab539 pthread_cond_wait + 48
3 data_flow 0x03ba02b2 boost::detail::condition_impl::do_wait(_opaque_pthread_mutex_t*) + 24
4 data_flow 0x03b9365b void boost::condition::do_wait<boost::recursive_mutex>(boost::recursive_mutex&) + 51
5 data_flow 0x03b96061 boost::threadpool::detail::pool_core<boost::threadpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks>::execute_task() volatile + 135
6 data_flow 0x03b96bba boost::threadpool::detail::worker_thread<boost::threadpool::detail::pool_core<boost::thre adpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> >::run() + 232
7 data_flow 0x03b9390b boost::_bi::bind_t<void, boost::_mfi::mf0<void, boost::threadpool::detail::worker_thread<boost::threadpool::detail::pool_core<boost::thre adpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> > >, boost::_bi::list1<boost::_bi::value<boost::shared_ptr<boost::threadpool::detail::worker_t hread<boost::threadpool::detail::pool_core<boost::threadpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> > > > > >::operator()() + 43
8 data_flow 0x03b95fd1 boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 79
9 data_flow 0x03ba1bc5 thread_proxy + 99
10 libSystem.B.dylib 0x90065155 _pthread_start + 321
11 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 36:
0 libSystem.B.dylib 0x900342ce semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x900662c6 _pthread_cond_wait + 1267
2 libSystem.B.dylib 0x900ab539 pthread_cond_wait + 48
3 data_flow 0x03ba02b2 boost::detail::condition_impl::do_wait(_opaque_pthread_mutex_t*) + 24
4 data_flow 0x03b9365b void boost::condition::do_wait<boost::recursive_mutex>(boost::recursive_mutex&) + 51
5 data_flow 0x03b96061 boost::threadpool::detail::pool_core<boost::threadpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks>::execute_task() volatile + 135
6 data_flow 0x03b96bba boost::threadpool::detail::worker_thread<boost::threadpool::detail::pool_core<boost::thre adpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> >::run() + 232
7 data_flow 0x03b9390b boost::_bi::bind_t<void, boost::_mfi::mf0<void, boost::threadpool::detail::worker_thread<boost::threadpool::detail::pool_core<boost::thre adpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> > >, boost::_bi::list1<boost::_bi::value<boost::shared_ptr<boost::threadpool::detail::worker_t hread<boost::threadpool::detail::pool_core<boost::threadpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> > > > > >::operator()() + 43
8 data_flow 0x03b95fd1 boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 79
9 data_flow 0x03ba1bc5 thread_proxy + 99
10 libSystem.B.dylib 0x90065155 _pthread_start + 321
11 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 37:
0 libSystem.B.dylib 0x900342ce semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x900662c6 _pthread_cond_wait + 1267
2 libSystem.B.dylib 0x900ab539 pthread_cond_wait + 48
3 data_flow 0x03ba02b2 boost::detail::condition_impl::do_wait(_opaque_pthread_mutex_t*) + 24
4 data_flow 0x03b9365b void boost::condition::do_wait<boost::recursive_mutex>(boost::recursive_mutex&) + 51
5 data_flow 0x03b96061 boost::threadpool::detail::pool_core<boost::threadpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks>::execute_task() volatile + 135
6 data_flow 0x03b96bba boost::threadpool::detail::worker_thread<boost::threadpool::detail::pool_core<boost::thre adpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> >::run() + 232
7 data_flow 0x03b9390b boost::_bi::bind_t<void, boost::_mfi::mf0<void, boost::threadpool::detail::worker_thread<boost::threadpool::detail::pool_core<boost::thre adpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> > >, boost::_bi::list1<boost::_bi::value<boost::shared_ptr<boost::threadpool::detail::worker_t hread<boost::threadpool::detail::pool_core<boost::threadpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> > > > > >::operator()() + 43
8 data_flow 0x03b95fd1 boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 79
9 data_flow 0x03ba1bc5 thread_proxy + 99
10 libSystem.B.dylib 0x90065155 _pthread_start + 321
11 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 38:
0 libSystem.B.dylib 0x900342ce semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x900662c6 _pthread_cond_wait + 1267
2 libSystem.B.dylib 0x900ab539 pthread_cond_wait + 48
3 data_flow 0x03ba02b2 boost::detail::condition_impl::do_wait(_opaque_pthread_mutex_t*) + 24
4 data_flow 0x03b9365b void boost::condition::do_wait<boost::recursive_mutex>(boost::recursive_mutex&) + 51
5 data_flow 0x03b96061 boost::threadpool::detail::pool_core<boost::threadpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks>::execute_task() volatile + 135
6 data_flow 0x03b96bba boost::threadpool::detail::worker_thread<boost::threadpool::detail::pool_core<boost::thre adpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> >::run() + 232
7 data_flow 0x03b9390b boost::_bi::bind_t<void, boost::_mfi::mf0<void, boost::threadpool::detail::worker_thread<boost::threadpool::detail::pool_core<boost::thre adpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> > >, boost::_bi::list1<boost::_bi::value<boost::shared_ptr<boost::threadpool::detail::worker_t hread<boost::threadpool::detail::pool_core<boost::threadpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> > > > > >::operator()() + 43
8 data_flow 0x03b95fd1 boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 79
9 data_flow 0x03ba1bc5 thread_proxy + 99
10 libSystem.B.dylib 0x90065155 _pthread_start + 321
11 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 39:
0 libSystem.B.dylib 0x900342ce semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x900662c6 _pthread_cond_wait + 1267
2 libSystem.B.dylib 0x900ab539 pthread_cond_wait + 48
3 data_flow 0x03ba02b2 boost::detail::condition_impl::do_wait(_opaque_pthread_mutex_t*) + 24
4 data_flow 0x03b9365b void boost::condition::do_wait<boost::recursive_mutex>(boost::recursive_mutex&) + 51
5 data_flow 0x03b96061 boost::threadpool::detail::pool_core<boost::threadpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks>::execute_task() volatile + 135
6 data_flow 0x03b96bba boost::threadpool::detail::worker_thread<boost::threadpool::detail::pool_core<boost::thre adpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> >::run() + 232
7 data_flow 0x03b9390b boost::_bi::bind_t<void, boost::_mfi::mf0<void, boost::threadpool::detail::worker_thread<boost::threadpool::detail::pool_core<boost::thre adpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> > >, boost::_bi::list1<boost::_bi::value<boost::shared_ptr<boost::threadpool::detail::worker_t hread<boost::threadpool::detail::pool_core<boost::threadpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> > > > > >::operator()() + 43
8 data_flow 0x03b95fd1 boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 79
9 data_flow 0x03ba1bc5 thread_proxy + 99
10 libSystem.B.dylib 0x90065155 _pthread_start + 321
11 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 40:
0 libSystem.B.dylib 0x900342ce semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x900662c6 _pthread_cond_wait + 1267
2 libSystem.B.dylib 0x900ab539 pthread_cond_wait + 48
3 data_flow 0x03ba02b2 boost::detail::condition_impl::do_wait(_opaque_pthread_mutex_t*) + 24
4 data_flow 0x03b9365b void boost::condition::do_wait<boost::recursive_mutex>(boost::recursive_mutex&) + 51
5 data_flow 0x03b96061 boost::threadpool::detail::pool_core<boost::threadpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks>::execute_task() volatile + 135
6 data_flow 0x03b96bba boost::threadpool::detail::worker_thread<boost::threadpool::detail::pool_core<boost::thre adpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> >::run() + 232
7 data_flow 0x03b9390b boost::_bi::bind_t<void, boost::_mfi::mf0<void, boost::threadpool::detail::worker_thread<boost::threadpool::detail::pool_core<boost::thre adpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> > >, boost::_bi::list1<boost::_bi::value<boost::shared_ptr<boost::threadpool::detail::worker_t hread<boost::threadpool::detail::pool_core<boost::threadpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> > > > > >::operator()() + 43
8 data_flow 0x03b95fd1 boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 79
9 data_flow 0x03ba1bc5 thread_proxy + 99
10 libSystem.B.dylib 0x90065155 _pthread_start + 321
11 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 41:
0 libSystem.B.dylib 0x900342ce semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x900662c6 _pthread_cond_wait + 1267
2 libSystem.B.dylib 0x900ab539 pthread_cond_wait + 48
3 data_flow 0x03ba02b2 boost::detail::condition_impl::do_wait(_opaque_pthread_mutex_t*) + 24
4 data_flow 0x03b9365b void boost::condition::do_wait<boost::recursive_mutex>(boost::recursive_mutex&) + 51
5 data_flow 0x03b96061 boost::threadpool::detail::pool_core<boost::threadpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks>::execute_task() volatile + 135
6 data_flow 0x03b96bba boost::threadpool::detail::worker_thread<boost::threadpool::detail::pool_core<boost::thre adpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> >::run() + 232
7 data_flow 0x03b9390b boost::_bi::bind_t<void, boost::_mfi::mf0<void, boost::threadpool::detail::worker_thread<boost::threadpool::detail::pool_core<boost::thre adpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> > >, boost::_bi::list1<boost::_bi::value<boost::shared_ptr<boost::threadpool::detail::worker_t hread<boost::threadpool::detail::pool_core<boost::threadpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> > > > > >::operator()() + 43
8 data_flow 0x03b95fd1 boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 79
9 data_flow 0x03ba1bc5 thread_proxy + 99
10 libSystem.B.dylib 0x90065155 _pthread_start + 321
11 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 42:
0 libSystem.B.dylib 0x900342ce semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x900662c6 _pthread_cond_wait + 1267
2 libSystem.B.dylib 0x900ab539 pthread_cond_wait + 48
3 data_flow 0x03ba02b2 boost::detail::condition_impl::do_wait(_opaque_pthread_mutex_t*) + 24
4 data_flow 0x03b9365b void boost::condition::do_wait<boost::recursive_mutex>(boost::recursive_mutex&) + 51
5 data_flow 0x03b96061 boost::threadpool::detail::pool_core<boost::threadpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks>::execute_task() volatile + 135
6 data_flow 0x03b96bba boost::threadpool::detail::worker_thread<boost::threadpool::detail::pool_core<boost::thre adpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> >::run() + 232
7 data_flow 0x03b9390b boost::_bi::bind_t<void, boost::_mfi::mf0<void, boost::threadpool::detail::worker_thread<boost::threadpool::detail::pool_core<boost::thre adpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> > >, boost::_bi::list1<boost::_bi::value<boost::shared_ptr<boost::threadpool::detail::worker_t hread<boost::threadpool::detail::pool_core<boost::threadpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> > > > > >::operator()() + 43
8 data_flow 0x03b95fd1 boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 79
9 data_flow 0x03ba1bc5 thread_proxy + 99
10 libSystem.B.dylib 0x90065155 _pthread_start + 321
11 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 43:
0 libSystem.B.dylib 0x900342ce semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x900662c6 _pthread_cond_wait + 1267
2 libSystem.B.dylib 0x900ab539 pthread_cond_wait + 48
3 data_flow 0x03ba02b2 boost::detail::condition_impl::do_wait(_opaque_pthread_mutex_t*) + 24
4 data_flow 0x03b9365b void boost::condition::do_wait<boost::recursive_mutex>(boost::recursive_mutex&) + 51
5 data_flow 0x03b96061 boost::threadpool::detail::pool_core<boost::threadpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks>::execute_task() volatile + 135
6 data_flow 0x03b96bba boost::threadpool::detail::worker_thread<boost::threadpool::detail::pool_core<boost::thre adpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> >::run() + 232
7 data_flow 0x03b9390b boost::_bi::bind_t<void, boost::_mfi::mf0<void, boost::threadpool::detail::worker_thread<boost::threadpool::detail::pool_core<boost::thre adpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> > >, boost::_bi::list1<boost::_bi::value<boost::shared_ptr<boost::threadpool::detail::worker_t hread<boost::threadpool::detail::pool_core<boost::threadpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> > > > > >::operator()() + 43
8 data_flow 0x03b95fd1 boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 79
9 data_flow 0x03ba1bc5 thread_proxy + 99
10 libSystem.B.dylib 0x90065155 _pthread_start + 321
11 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 44:
0 libSystem.B.dylib 0x900342ce semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x900662c6 _pthread_cond_wait + 1267
2 libSystem.B.dylib 0x900ab539 pthread_cond_wait + 48
3 data_flow 0x03ba02b2 boost::detail::condition_impl::do_wait(_opaque_pthread_mutex_t*) + 24
4 data_flow 0x03b9365b void boost::condition::do_wait<boost::recursive_mutex>(boost::recursive_mutex&) + 51
5 data_flow 0x03b96061 boost::threadpool::detail::pool_core<boost::threadpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks>::execute_task() volatile + 135
6 data_flow 0x03b96bba boost::threadpool::detail::worker_thread<boost::threadpool::detail::pool_core<boost::thre adpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> >::run() + 232
7 data_flow 0x03b9390b boost::_bi::bind_t<void, boost::_mfi::mf0<void, boost::threadpool::detail::worker_thread<boost::threadpool::detail::pool_core<boost::thre adpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> > >, boost::_bi::list1<boost::_bi::value<boost::shared_ptr<boost::threadpool::detail::worker_t hread<boost::threadpool::detail::pool_core<boost::threadpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> > > > > >::operator()() + 43
8 data_flow 0x03b95fd1 boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 79
9 data_flow 0x03ba1bc5 thread_proxy + 99
10 libSystem.B.dylib 0x90065155 _pthread_start + 321
11 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 45:
0 libSystem.B.dylib 0x900342ce semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x900662c6 _pthread_cond_wait + 1267
2 libSystem.B.dylib 0x900ab539 pthread_cond_wait + 48
3 data_flow 0x03ba02b2 boost::detail::condition_impl::do_wait(_opaque_pthread_mutex_t*) + 24
4 data_flow 0x03b9365b void boost::condition::do_wait<boost::recursive_mutex>(boost::recursive_mutex&) + 51
5 data_flow 0x03b96061 boost::threadpool::detail::pool_core<boost::threadpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks>::execute_task() volatile + 135
6 data_flow 0x03b96bba boost::threadpool::detail::worker_thread<boost::threadpool::detail::pool_core<boost::thre adpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> >::run() + 232
7 data_flow 0x03b9390b boost::_bi::bind_t<void, boost::_mfi::mf0<void, boost::threadpool::detail::worker_thread<boost::threadpool::detail::pool_core<boost::thre adpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> > >, boost::_bi::list1<boost::_bi::value<boost::shared_ptr<boost::threadpool::detail::worker_t hread<boost::threadpool::detail::pool_core<boost::threadpool::prio_task_func, boost::threadpool::prio_scheduler, boost::threadpool::static_size, boost::threadpool::resize_controller, boost::threadpool::wait_for_all_tasks> > > > > >::operator()() + 43
8 data_flow 0x03b95fd1 boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 79
9 data_flow 0x03ba1bc5 thread_proxy + 99
10 libSystem.B.dylib 0x90065155 _pthread_start + 321
11 libSystem.B.dylib 0x90065012 thread_start + 34
Thread 46:
0 libSystem.B.dylib 0x900342ce semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x900662c6 _pthread_cond_wait + 1267
2 libSystem.B.dylib 0x900ab539 pthread_cond_wait + 48
3 data_flow -
Images Appear Different When Viewed in Photoshop CS4 vs. LR 2.7
Hello, I hope someone on this forum can help.
I have a series of high quality images that are catalogued using Lightroom 2.7. Many were edited using Photoshop while others were edited in the "Develop" module of Lightroom. All of the images look exceptional in both Lightroom and Brdige. However, when I open some of the images in PS, either directly from Bridge or by using the "Edit in" command from Lightroom, they appear washed out and dull -- very different and much worse. I always use the setting, "Edit a Copy with Lightroom Adjustments." The problem pertains to all images regardless of file format (JPEG, DNG, NEF, etc.) and regardless of whether they are opened from LR, Bridge or directly from the image using the "Open with" command in Windows.
This happens on two completely different set of monitors. At work I have a Dell 2208 WFPt UltraSharp monitor, and at home a dual monitor setup with an Asus VE278Q and an LG flat screen (all are flat screen, high quality monitors). I have a Lenovo X201s with 8gb of RAM and a high-speed i7 processor running Windows 7, 64-bit. All of my Adobe products are up-to-date. Windows Color Management shows all displays as "Generic PnP Monitor - Intel HD Graphics," and the Advanced mode of Intel's HD Graphics correctly identifies each monitor being used. The problem is identical regardless of which monitor is being used and it does not seem to make any difference as to which color profile is associated with the monitor (I have two profiles added -- Adobe RGB (1998) (the default) and sRGB IEC61966-2.1).
Specifically, if I double-click on a particular TIF image in Bridge (where the preview looks great), it then triggers Camera Raw 5.7 - TIF, where again the image looks terrific. The settings applied by Camera Raw are "ProPhotoRGB; 16 bit; 3607 by 2420 (8.7MP); 300 ppi" (although changing these settings makes no difference whatever when the image is subsequently opened in Photoshop). When the image is opened in Photoshop it looks terrible -- dull and washed out. I encounter the exact same problem when using my dual monitor setup at home, so I don't think monitor calibrations are the cause.
Strangely, I don't think this problem existed a couple of months ago. I've been busy on a project and haven't used Photoshop since the end of this past July (of 2011). As I recall, this problem did not exist then, so I'm wondering if a setting in Photoshop inadvertently got altered since then.
I have the following key settings in Photoshop's "Color Settings":
Working Spaces: RGB -- ProPhoto RGB
Color Management Policies -- Preserve Embedded Profiles
Conversion Options -- Adobe (ACE)
I have the following key settings in Lightroom's "Preferences / External Editing":
Edit in Adobe Photoshop CS4
File Format -- PSD; Color Space ProPhoto RGB, 16-bits, 300 dpi
File Format -- TIFF; Color Space ProPhoto RGB, 16-bits, 300 dpi
I have tried and tried to figure this out, to no avail. Any help would be greatly appreciated!
Bob Woods
St. Paul, MinnesotaThanks, I think you're right.
Any suggestions for a cheap and easy way to calibrate my monitors?
Maybe you are looking for
-
Help required in Weblogic 6 - Creation & Configuration of Web Application
Forum Home > Enterprise JavaBeans[tm] Topic: Help required in Weblogic 6 - Creation & Configuration of Web Application Duke Dollars 2 Duke Dollars assigned to this topic. Reward the best responses to your question using the icons below, or transfer a
-
Toner Rubbing off of Print on 9040dn Printer
Hello, I am a desktop support technician and I am having trouble with a 9040dn printer. The letters on the print feel raised, and if you rub it for a couple of seconds, it will start to come off. This happens mostly when using bond paper, but some
-
Can't burn more than 2 hours using DVDSP 4
I am having trouble burning my project to a DVD. I have created 2 Quicktime.dv movies, in iMovie, that are approximately 1 hour 10 minutes each. I have taken the bitrate, in Preferences, all the way down to 2.0, using One Pass, and all I get is the m
-
How To Disable Verify Database Message Alert
How To Disable Verify Database Message Alert? I have a VB6 open Crystal Reports using Crystal Reports XI R2 (SP5) and almost every time I open a report, I get an alert message about the table has been changed and I have to click "Ok" to make it goes
-
Hi all... All the talk is about the new 3G iPhone coming out next - which I will must likely get - but when is the 2.0 os for the current iPhone out? is it coming out the same time as the new handset or sooner? Sorry if I've missed the obvious answer