Photoshop collapsing

Hi . when i try render 3D images to higher resuoltion the potoshop CC softwaer either collapsing or give me amessage that i dont have sufficsent RAM MEMORY
i Have 4GB and installed the Photoshop CC 64 bit so it would extract more out of my memory . please help me

Hi M@tt@n2400,
I have moved this discussion to the Photshop General forum, where you should be able to get more help on this issue.
Alec

Similar Messages

Adobe Photoshop CS3 collapse each time it load a big file

I was loading a big file of photos from iMac iPhoto to Adobe Photoshop CS3 and it keep collapsing, yet each time I reopen photoshop it load the photos again and collapse again. is there a way to stop this cycle?

I don't think that too many users here actually use iPhoto (even the Mac users)
However, Google is your friend. A quick search came up with some other non-Adobe forum entries:
.... but the golden rule of iPhoto is NEVER EVER MESS WITH THE IPHOTO LIBRARY FROM OUTSIDE IPHOTO.In other words, anything you might want to do with the pictures in iPhoto can be done from *within the program,* and that is the only safe way to work with it. Don't go messing around inside the "package" that is the iPhoto Library unless you are REALLY keen to lose data, because that is exactly what will happen.
.....everything you want to do to a photo in iPhoto can be handled from *within the program.* This INCLUDES using a third-party editor, and saves a lot of time and disk space if you do this way:
1. In iPhoto's preferences, specify a third-party editor (let's say Photoshop) to be used for editing photos.
2. Now, when you right-click (or control-click) a photo in iPhoto, you have two options: Edit in Full Screen (ie iPhoto's own editor) or Edit with External Editor. Choose the latter.
3. Photoshop will open, then the photo you selected will automatically open in PS. Do your editing, and when you save (not save as), PS "hands" the modified photo back to iPhoto, which treats it exactly the same as if you'd done that stuff in iPhoto's own editor and updates the thumbnail to reflect your changes. Best of all, your unmodified original remains untouched so you can always go back to it if necessary.

I was loading a big file of photos from iPhoto to Adobe Photoshop CS3 and it keep collapsing, yet each time I reopen photoshop it load the photos again and cal laps again. is there a way to stop this cycle?

I was loading a big file of photos from iPhoto to Adobe Photoshop CS3 and more then midway it keep collapsing, yet each time I re-open photoshop to load a small amount of photos, it load the previous photos again, and again it collapse. is there a way to stop this cycle and start a new?

http://helpx.adobe.com/photoshop.html

Collapsing panel in Photoshop issue

hi,
I have a CS SDK panel deployed in all the 3 applications - Photoshop, Illustrator and InDesign. My panel has a login component and users need to log in before using it.
1) In Photoshop, when a logged in user collapses the panel, works on Photoshop and activates the collapsed icon, the panel goes back to the login screen and they are forced to login every time. This behavior does not occur in Indesign and Illustrator.
Can you please tell me if there are any workarounds for this issue?
Other discrepencies between the apps -
2) In Illustrator, when the panel is closed entirely and re-opened under Extensions > <panel name>, users are not taken back to the login screen. They are forced to quit Illustrator and restart it in order to re-login to the panel. This does not happen in InDesign and Photoshop.
thanks for any help in this regard.

As you've found, each application behaves differently with respect to lifecycle of the extension. Here we have a range of behaviors - on one end of the spectrum we have Photoshop which greedily unloads extensions whenever possible, and at the other end we have Illustrator which doesn’t unload an extension when it is closed through the UI.
For #1, you have a couple of choices.
Maintain the state of your extension somewhere that will persist between loading/unloading (e.g. on disk). When your extension is loaded, check this persistent state to see which UI you should present to the user.
Use CSXSInterface.evalScript(“PhotoshopPersistent”) which will prevent Photoshop from unloading the panel when it is collapsed.
For #2, you theoretically shouldn’t have to login again, since your panel has not be unloaded. As far as I know, Illustrator does not expose a similar mechanism for forcing an unload, although the Illustrator forum may be a better place to get a more definitive answer.

After hiding photoshop and returning, all collapsed document windows uncollapse

Hi,
I'm on Photoshop CS6 with my documents in the 'float all in wondows' view. I have say 20 documents open, 19 collapsed into the dock with the one document left i'm working on. I hide photoshop to go to the desktop, click back into photoshop when done. As i return to photoshop all of the previously collapsed documents reappear one by one and fill up my workspace. I then need to collapse all of my documents once again to leave just the one I'm working on. This was never an issue in earlier versions, does anyone know how to override? thanks.

I'm assuming you're on a Mac. That is a Mac OS native feature. I'm afraid you can't disable that from Photoshop.
Alternatively, 2 workarounds I see here:
Instead of 'floating' your documents individually, why don't you tab them together and switch between them using tabs?
This way, all your documents will be open within 1 parent container, you can switch between them using Cmd + ` or Shift + Cmd + ` (backwards)
Another option you could try in your current workflow is not to 'Hide Photoshop'. Set a 'Hot Corner' in Mac OS to 'Show Desktop'. For example, the way my workflow is setup is - it will show Desktop when I move my mouse over to the extreme top left corner. To do this, Mac OS > System Preferences > Desktop & Screensaver > Screensaver > Hot Corners

How do I open up collapsed version sets in Photoshop Elements 13?

How do you open up collapsed version sets in Photoshop 13?

Switch from the new thumbnail display to the old one, which shows the file names and details. Your version set and stack icons will appear like before. Shortcut Ctrl D /Cmd D.

Photoshop Elements 7 folder layer doesn't wanted to collapse. Need help!

Hi all,
Recently i purchased a catalog online, it is under .psd format and i assumed that everything is covered in layer which is editable.
Not until then i downloaded and most of the content are under folder. Others work fine which i saw in internet tutorial which just only double click on it and they will show a drop down box.
But in PSE7 , it doesn't. Instead, they asked me to rename it.
I screenshot them and please refer below.
I am working on window 7 OS btw

Photoshop elements doesn't normally allow users to open, close or edit layer groups (layer sets), which are usually made in the full version of photoshop ( i.e. cs6 or cc2014)
If you notice the pencil icon with slash to the right of the folder name in the layers panel means that layer group is not editable in pse 7.
If you want to edit the layer groups you might use this action from over on elements village:
Opening layer sets in PSE7 - Elements Village
Or check out Elements+
Ungrouping Layers

Cannot collapse layer groups in Photoshop CC 2014.

Any solutions out there? Used to be able to just click the arrow next to the folder. That does not seem to work anymore.

I guess when you said "Extension Manager", actually you mean "Adobe Exchange Panel". This panel is Flash-based, which is not supported by PS CC 2014. Now you have to click "Help"->"Browse Add-Ons..." menu item to browse and download/install extensions. Note that you should ensure Adobe Creative Cloud application is running and "File Sync" is on in its Preferences dialog.

Photoshop CS2

since Adobe Photoshop CS2 was installed I had so many troubles. It's very slow, and it takes up to 10 minutes to pen an image, as I'm working in huge files. Moreover, it keeps haning and crashing, and collapses out of the sudden without any error messages.

Hello,
Thank you for helping.
huge images: I meant images size is big, more than 1 GB.
OS: Windows 7, installed in 32 bits.
Hardware: HP HighEnd
                 RAM 8.00 GB
                 IntelXeon 5672 3.2GHz
                 Manufacturere: Hewlett-Packard
                 Model: HP Z800 Workstation
                 Model number: FF825AV
There is no reports at all, the application suddenly closes.
We have other machines that use the same OS, they have the same specifications, although CS2 is functioning properly.
Regards.

Photoshop Elements 8 for Mac Question about Opening Files

Hi. I somehow must have changed some settings in Photoshop Elements and I don't know how to change them back. Whenever I open an image, it opens at a size of 34.5% and the window is sized accordingly. When I change the view to Actual Pixels, the image gets bigger but the window stays the same size as before so I need to manually resize the window. Anyway, I don't know how I accidentally set these settings as the default. I'd like Photoshop Elements to open images at 100% and have the window size be the same. Does anyone know how I can fix it? Thanks.

Elements will open an image at the largest size it can so that the whole image fits in the Active Image Area. It's the same as Fit on Screen view.
You can make the Active Image Area larger by collapsing Panels and the Project Bin.
To get your window to resize with your photo you need to choose a Preference. Go up to the Photoshop Elements menu (Edit menu for Windows users) and choose Preferences > General and click on the box next to Zoom Resizes Windows. Click OK.
Hope that Helps!
Rick
essential-photoshop-elements.com

How can I set CameraRAWOpenOptions using Javascripts in Photoshop CS6?

I have been unable to set CameraRAWOpenOptions in scripts that worked fine for me in Photoshop CS5 but now do not work in Photoshop CS6. There are no error messages when I run the scripts, and they appear to finish okay, but the images come out unadjusted. Below is the essence of how I'm trying to do it. When I run these scripts in Extendscript (CS5 or CS6 does not make a difference), Photoshop CS6 simply uses its own default (saved) settings, but CS5 would allow the overrides. I did change the default settings in CameraRAW in CS6 to use the default lens correction profiles available from the EXIF data, and I'm wondering if that rendered the script unable to change any of the rest of the settings.
Here's how I have the code:
var RawOptions = new CameraRAWOpenOptions;
RawOptions.settings=CameraRAWSettingsType.CUSTOM;
RawOptions.exposure=+2.00;
RawOptions.vignettingAmount = 0;
RawOptions.vignettingMidpoint = 0;
RawOptions.contrast = 50;
RawOptions.saturation = 0;
RawOptions.shadows = 0;
RawOptions.luminanceSmoothing = 0;
var JPGopts = new JPEGSaveOptions;
JPGopts.quality = JPEGquality;
//Perform the loop through the files
app.open(testListing[0], RawOptions, false);
app.activeDocument.close(SaveOptions.DONOTSAVECHANGES);
for (var nfile = nstart; nfile < nstop; nfile++)
    app.open(testListing[nfile], RawOptions, false);
    FnameSave = new File(SavePath+"/"+testListing[nfile].name);
    app.activeDocument.saveAs(FnameSave, JPGopts, false, Extension.UPPERCASE);
    app.activeDocument.close(SaveOptions.DONOTSAVECHANGES);

I would collapse and expand the toolbar windows by using the double arrow icon?
Doing this will almost give you your full screen?
Or you can hit 'Tab' and it hides your tools when you don't need them?

Combine text layers but keep text editable? OR A way to export text as a paragraph in InDesign into Photoshop

Hoping to achieve one of these goals, either option is equally fine:
Option 1) find a way to merge text layers but keep the text editable in Photoshop.
Option 2) find a way in InDesign to group and collapse text so that it lands on one layer or one text paragraph that could be selected together. So that when I export to EPS and then PSD the text is not sliced up on various layers but is combined into one editable text layer.
Why? I'm saving out from InDesign and for whatever reason the text is fragmented across many objects/layers/ whatever you want to call it. When using the export feature from InDesign these bits of text are then saved out as separate layers when you export to EPS. Using Illustrator with the EPS files is no help either.
The best way I can describe it is like in these InDesign document there are web page slices being used and various bits of the text are landing on various slices which in turn befuddles the export function that is valiantly trying to maintain these 'slices' of text by fragmenting letters, words, or characters across many 'slices' into many layers.
Here's what the document looks like when I go from InDesign> export> EPS> then open in Illustrator and export to PSD.
What I want is all of those individual text layers to be one text layer, still editable, in Photoshop.

http://www.automatication.com/index.php?id=13
Bob

Photoshop CS5 Mini Bridge Annoying Beep

I have an annoying issue with the Mini Bridge in Photoshop CS5, and I believe anyone could reproduce it if you do the following:
Open Photoshop CS5.
Have the Mini Bridge palette collapsed as an icon, docked somewhere (you can simply use the "Photography" workspace to do that).
Open anything, perhaps a new document.
Click on the Mini Bridge palette icon to open the Mini Bridge. Wait until it loads.
Then click on the same Mini Bridge icon again to collapse it.
Make sure your speakers are on.
Now press Space as you would do to pan around the document. You don't have to pan, it's enough to just press Space.
You will hear a beep sound, which you usually hear when OS X tells you that you're clicking an inactive window, or typing in a window that does not accept keyboard input, or in other similar situations. The beep will sound repeatedly while you hold Space down to pan around. It will sound each and every time you press space from then on, until you interact with the document using some other tool (like drawing something with the brush tool). Then the sound no longer happens when panning again.
The problem has occasionally happened to me when using other collapsed iconic palettes as well, however, I cannot always reproduce them.
This is a small issue that doesn't affect workflow, but having to click extra tools just to get rid of the beeping sound is very annoying, enough to make me not use the Mini Bridge.
I'm running Snow Leopard.
If anyone else can reproduce the issue, please post here. I can reproduce it every single time.

>But that's still not a proper solution.
we're not in a very good situation to know what or when Adobe will respond. We know that they are aware of many bugs but since history is all we have, CS4 had only 1 update before CS5 was released and we've already had that same first quarter update. So, without any more information I can only assume that the next fix will be after CS6 is released.
I know that Adobe can't discuss future plans...... but what Adobe can and can not do is up to them. So if Adobe wanted to announce an upcoming fix they could ( and they have in the past ). I can understand keeping new product releases under wraps, but this is just a fix for something that .... well..... we have already purchased.
>Just go to Mac 'System Preferences' - 'Sound', set the volume of the error beep to minimum and forget about it.
So, yes I have had the error sound set to "funk" and on very low for quite a while, which results in a low clicking sound.
Again, I feel like I need to repeat this, I like CS5, love PS, but some things can be better, and isn't that why we are all here. It just seems odd that you can purchase something today that has bugs but can't ask the vendor when it will be fixed?
regards.

Exporting Photoshop LUTs for use in Speedgrade

Hi
I'm not sure if this is a silly question, but here goes!
Firstly, I'm using Windows 7.
I have created an adjustment layer in Photoshop CC 2014 and exported to 3DL, CSP, CUBE files and ICC profile.
How do I pick up and use these in Speedgrade CC 2014?
Thanks!
Dave

well I tried. I created the Photoshop adjustment layer, exported as Color Lookup Tables using all 4 formats of 3DL, CUBE, CSP and ICC Profile
then in Speedgrade, did the +, FILM, LUT and immediately it adds the LUT to my layer list
I do not see the .... button next to the pulldown list - I don't think I get a pulldown list ??
RoninEdits wrote:
in speedgrade, the bottom left layers area, click the + button and from the menu choose Film>Lut. you can then click the .... button next to the lookup table pulldown list to choose your custom lut.
EDIT - got it, sorry. Had to collapse LOOK Management to see Lookup Table and the ... button!
my 3DL seems fine
my CSP is red and white checker board
my CUBE is fine
and my ICC is darker then original ,,,, I see what you mean Dave about the very high contrast/saturation

Photoshop 11.0.1 stall in Mac OS X 10.5.8 – what is happening? (got sample)

Hi!
Yesteday a retoucher here at work came to me wondering if I could do something about his stalled Photoshop. It was read in Activity Monitor and had been like that for several minutes. I think he tried to save or something.
Can someone take a look at the sample for Photoshop and give a hint on what it's doing?
Below is the sample:
Sampling process 7706 for 3 seconds with 1 millisecond of run time between samples
Sampling completed, processing symbols...
Analysis of sampling Adobe Photoshop CS4 (pid 7706) every 1 millisecond
Call graph:
    16 Thread_2507
      16 0x3839
        16 0x3912
          16 0x220736
            16 0x2206aa
              16 0x6222f
                16 0x63ed3
                  16 0x63d65
                    16 0x69906
                      16 0x6b9da
                        16 0x9c1754
                          16 0x9ba383
                            16 0x9ba24a
                              16 0x9ba11a
                                16 0x9b94fb
                                  16 0x9b94c1
                                    16 0x9b9454
                                      16 0x9b700d
                                        16 0x204e84
                                          16 0x204d99
                                            16 AWS_CUI_CreateSaveDialog(long*, adobe::aws::gen::String<unsigned short>&, char, adobe::q::QDocument&)
                                              16 AWS_CUI_CreateSaveDialog(long*, adobe::aws::gen::String<unsigned short>&, char, adobe::q::QDocument&)
                                                16 0xb56ede
                                                  16 pthread_cond_wait
                                                    16 _pthread_cond_wait
                                                      16 semaphore_wait_signal_trap
                                                        16 semaphore_wait_signal_trap
    16 Thread_2603
      16 thread_start
        16 _pthread_start
          9 __monitor_file_descriptor__
            9 __monitor_file_descriptor__
          7 kevent
            7 kevent
    16 Thread_2703
      16 thread_start
        16 _pthread_start
          16 AMTThread::Worker(void*)
            16 _AMTThreadedPCDService::PCDThreadWorker(_AMTThreadedPCDService*)
              16 AMTConditionLock::LockWhenCondition(int)
                16 pthread_cond_wait
                  16 _pthread_cond_wait
                    16 semaphore_wait_signal_trap
                      16 semaphore_wait_signal_trap
    16 Thread_2803
      16 thread_start
        16 _pthread_start
          16 glvmDoWork
            16 pthread_cond_wait$UNIX2003
              16 __semwait_signal
                16 __semwait_signal
    16 Thread_2903
      16 thread_start
        16 _pthread_start
          16 PrivateMPEntryPoint
            16 0x1e032eff
              16 MPWaitOnSemaphore
                16 semaphore_timedwait_trap
                  16 semaphore_timedwait_trap
    16 Thread_2a03
      16 thread_start
        16 _pthread_start
          16 PrivateMPEntryPoint
            16 0x1e032eff
              16 MPWaitOnSemaphore
                16 semaphore_timedwait_trap
                  16 semaphore_timedwait_trap
    16 Thread_2b03
      16 thread_start
        16 _pthread_start
          16 PrivateMPEntryPoint
            16 0x1e032eff
              16 MPWaitOnSemaphore
                16 semaphore_timedwait_trap
                  16 semaphore_timedwait_trap
    16 Thread_2c03
      16 thread_start
        16 _pthread_start
          16 PrivateMPEntryPoint
            16 0x27c0d85
              16 0x27c138d
                16 MPWaitOnQueue
                  16 TSWaitOnConditionTimedRelative
                    16 TSWaitOnCondition
                      16 pthread_cond_wait$UNIX2003
                        16 __semwait_signal
                          16 __semwait_signal
    16 Thread_2d03
      16 thread_start
        16 _pthread_start
          16 PrivateMPEntryPoint
            16 0x27c0d85
              16 0x27c138d
                16 MPWaitOnQueue
                  16 TSWaitOnConditionTimedRelative
                    16 TSWaitOnCondition
                      16 pthread_cond_wait$UNIX2003
                        16 __semwait_signal
                          16 __semwait_signal
    16 Thread_2e03
      16 thread_start
        16 _pthread_start
          16 PrivateMPEntryPoint
            16 0x27c0d85
              16 0x27c138d
                16 MPWaitOnQueue
                  16 TSWaitOnConditionTimedRelative
                    16 TSWaitOnCondition
                      16 pthread_cond_wait$UNIX2003
                        16 __semwait_signal
                          16 __semwait_signal
    16 Thread_2f03
      16 thread_start
        16 _pthread_start
          16 ScObjects::Thread::go(void*)
            16 ScObjects::BridgeTalkThread::run()
              15 ScObjects::BridgeTalkThread::run()
              1 ScObjects::Thread::wait(unsigned int)
                1 ScObjects::Thread::sleep(unsigned int)
                  1 nanosleep
                    1 mach_wait_until
                      1 mach_wait_until
    16 Thread_3003
      16 thread_start
        16 _pthread_start
          16 thread_proxy
            16 boost::function0<void, std::allocator<boost::function_base> >::operator()() const
              16 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()()
                16 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()
                  16 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
                    16 void boost::condition::do_wait<boost::recursive_mutex>(boost::recursive_mutex&)
                      16 boost::detail::condition_impl::do_wait(_opaque_pthread_mutex_t*)
                        16 pthread_cond_wait
                          16 _pthread_cond_wait
                            16 semaphore_wait_signal_trap
                              16 semaphore_wait_signal_trap
    16 Thread_3103
      16 thread_start
        16 _pthread_start
          16 thread_proxy
            16 boost::function0<void, std::allocator<boost::function_base> >::operator()() const
              16 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()()
                16 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()
                  16 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
                    16 void boost::condition::do_wait<boost::recursive_mutex>(boost::recursive_mutex&)
                      16 boost::detail::condition_impl::do_wait(_opaque_pthread_mutex_t*)
                        16 pthread_cond_wait
                          16 _pthread_cond_wait
                            16 semaphore_wait_signal_trap
                              16 semaphore_wait_signal_trap
    16 Thread_3203
      16 thread_start
        16 _pthread_start
          16 thread_proxy
            16 boost::function0<void, std::allocator<boost::function_base> >::operator()() const
              16 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()()
                16 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()
                  16 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
                    16 void boost::condition::do_wait<boost::recursive_mutex>(boost::recursive_mutex&)
                      16 boost::detail::condition_impl::do_wait(_opaque_pthread_mutex_t*)
                        16 pthread_cond_wait
                          16 _pthread_cond_wait
                            16 semaphore_wait_signal_trap
                              16 semaphore_wait_signal_trap
    16 Thread_3303
      16 thread_start
        16 _pthread_start
          16 thread_proxy
            16 boost::function0<void, std::allocator<boost::function_base> >::operator()() const
              16 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()()
                16 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()
                  16 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
                    16 void boost::condition::do_wait<boost::recursive_mutex>(boost::recursive_mutex&)
                      16 boost::detail::condition_impl::do_wait(_opaque_pthread_mutex_t*)
                        16 pthread_cond_wait
                          16 _pthread_cond_wait
                            16 semaphore_wait_signal_trap
                              16 semaphore_wait_signal_trap
    16 Thread_3403
      16 thread_start
        16 _pthread_start
          16 PrivateMPEntryPoint
            16 0xfd1d1af6
              16 0xfd1d21f8
                16 MPWaitOnQueue
                  16 TSWaitOnConditionTimedRelative
                    16 TSWaitOnCondition
                      16 pthread_cond_wait$UNIX2003
                        16 __semwait_signal
                          16 __semwait_signal
    16 Thread_3503
      16 thread_start
        16 _pthread_start
          16 PrivateMPEntryPoint
            16 0xfd1d1af6
              16 0xfd1d21f8
                16 MPWaitOnQueue
                  16 TSWaitOnConditionTimedRelative
                    16 TSWaitOnCondition
                      16 pthread_cond_wait$UNIX2003
                        16 __semwait_signal
                          16 __semwait_signal
    16 Thread_3603
      16 thread_start
        16 _pthread_start
          16 PrivateMPEntryPoint
            16 0xfd1d1af6
              16 0xfd1d21f8
                16 MPWaitOnQueue
                  16 TSWaitOnConditionTimedRelative
                    16 TSWaitOnCondition
                      16 pthread_cond_wait$UNIX2003
                        16 __semwait_signal
                          16 __semwait_signal
    16 Thread_3703
      16 thread_start
        16 _pthread_start
          16 0xfd0f5486
            16 EntryFM
              16 0xfd04654a
                16 pthread_cond_wait
                  16 _pthread_cond_wait
                    16 semaphore_wait_signal_trap
                      16 semaphore_wait_signal_trap
    16 Thread_3803
      16 thread_start
        16 _pthread_start
          16 0xfd0f5486
            16 EntryFM
              16 0xfd04654a
                16 pthread_cond_wait
                  16 _pthread_cond_wait
                    16 semaphore_wait_signal_trap
                      16 semaphore_wait_signal_trap
Total number in stack (recursive counted multiple, when >=5):
        19       _pthread_start
        19       thread_start
        9       PrivateMPEntryPoint
        8       _pthread_cond_wait
        8       pthread_cond_wait
        8       semaphore_wait_signal_trap
        7       __semwait_signal
        7       pthread_cond_wait$UNIX2003
        6       MPWaitOnQueue
        6       TSWaitOnCondition
        6       TSWaitOnConditionTimedRelative
Sort by top of stack, same collapsed (when >= 5):
        semaphore_wait_signal_trap        128
        __semwait_signal        112
        semaphore_timedwait_trap        48
        ScObjects::BridgeTalkThread::run()        15
        __monitor_file_descriptor__        9
        kevent        7
Sample analysis of process 7706 written to file /dev/stdout

There's not enough information there to tell all the details.
But it looks like Photoshop called the OS for something, and is waiting for the OS to return.
Now, the odd part is that the samples only account for 16 milliseconds out of 3000 milliseconds -- which means that the Photoshop application was completely blocked by the OS.
We have seen behavior similar to that before when the OS disk buffers decided that they wanted to flush gigabytes of data -- but Apple supposedly fixed that bug in 10.5.0.
My guess is that you are waiting on a disk or some other device driver that is really, really unhappy (disk going bad, tablet cable broken, etc.).

Photoshop collapsing

Similar Messages

Maybe you are looking for