LAbview crashing after long test

Hi,
I was wondering if anyone else has experienced this problem. I am
running a long test (about 6 hours) and I am finding before it gets to
the end, Labview shuts down. It is fine if I run the shorter version of
the test and I am 99% sure it isn't anything in my program since it is
all just repeating the same loop over and over again for different
permutations of data (and since it doesn't crash in one particular
spot).
Any ideas? Suggestions?
Thanks
Jenni
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

Thanks for your reply!
Yes, I did check all of those things that you mentioned and don't think
that any of them really apply. Do you think that it could be because of
insufficient memory and/or Virtual memory since so many resources would
likely be allocated during a long test?
Thanks
jenni
In article <7nmuvd$hsv$[email protected]>,
"Richard Jones" wrote:
> Other things outside of Labview might be causing it.
> Have you checked things like screensavers, automated virus scans, misc
> network activity, bored security guard using PC to surf net after
hours...
> Just some ideas...
>
> [email protected] wrote in message <7nmsid$ppi$[email protected]>...
> >Hi,
> >
> >I was wondering if anyone else has experienced this p
roblem. I am
> >running a long test (about 6 hours) and I am finding before it gets
to
> >the end, Labview shuts down. It is fine if I run the shorter version
of
> >the test and I am 99% sure it isn't anything in my program since it
is
> >all just repeating the same loop over and over again for different
> >permutations of data (and since it doesn't crash in one particular
> >spot).
> >
> >Any ideas? Suggestions?
> >
> >Thanks
> >Jenni
> >
> >
> >Sent via Deja.com http://www.deja.com/
> >Share what you know. Learn what you don't.
>
>
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

Similar Messages

QTP crashes after long cycle runs

Product name: QuickTest Professional
Product version: 11.00
Product ID: QTPRPID11.00/01
Product build: 1018
Operating system: Microsoft Windows 7 Service Pack 1 (Build 7601)
Internet Explorer version: 9.0.8112.16421
Addins Used
.NET
Web
Problem Statement
QTP Crashes after running successfully for 180 Hours (36 Cycles)
Script Started Time - 2014-05-05 04:33:20
QTP Started to Hang Time- 2014-05-11 17:12:04
We need your Expert Advice for Improving the Performance of the QTP,
Suspect –(Possible Causes)
We would like to know , if the below mentioned setting would affect the performance of the QTP scripts in any way?
We are currently having the 2 major vbs files in QTP Scripts. Each vbs File has around 17000 lines of Code with around 160 functions. And these are loaded at the Beginning of the Automation scriptrun (Not Run Time)
And we load shared Repositories at the start of the QTP run which is about 20MB.
Will this below Corrective action Help?
if we implement the below changes, will be any considerable improvement in the Performance ?
By reducing the No. of lines in the VBS file by splitting the 17000lines VBS File into smaller Files
by loading the Functions and the Repositories in the Run Time Dynamically.

Create a new profile as a test to check if your current profile is causing the problem.
See "Creating a profile":
*https://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-profiles
*http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Profile_issues
If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over the problem
*http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_Firefox
Boot the computer in Windows Safe Mode with network support (press F8 on the boot screen) as a test.
*http://www.bleepingcomputer.com/tutorials/how-to-start-windows-in-safe-mode/
Do a malware check with several malware scanning programs on the Windows computer. 
Please scan with all programs because each program detects different malware. 
All these programs have free versions.
Make sure that you update each program to get the latest version of their databases before doing a scan.
*Malwarebytes' Anti-Malware: http://www.malwarebytes.org/mbam.php
*AdwCleaner: http://www.bleepingcomputer.com/download/adwcleaner/ http://www.softpedia.com/get/Antivirus/Removal-Tools/AdwCleaner.shtml
*SuperAntispyware: http://www.superantispyware.com/
*Microsoft Safety Scanner: http://www.microsoft.com/security/scanner/en-us/default.aspx
*Windows Defender: http://windows.microsoft.com/en-us/windows/using-defender
*Spybot Search & Destroy: http://www.safer-networking.org/en/index.html
*Kasperky Free Security Scan: http://www.kaspersky.com/security-scan
You can also do a check for a rootkit infection with TDSSKiller.
*Anti-rootkit utility TDSSKiller: http://support.kaspersky.com/5350?el=88446
See also:
*"Spyware on Windows": http://kb.mozillazine.org/Popups_not_blocked

Labview crashing during long program

Hi,
I am having a problem with Labview shutting itself down after it is
running for a long time. I am running a test that takes about 6 hours.
I am confident that it isn't my code that is causing the failure since
it just executes the same loop over and over with different permutations
of data.
I was just wondering if anyone else has experienced similar problems and
if anyone has any suggestions?
Thanks a lot
Jenni
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

At the Users Group here in Portland some time back, there was mention of an
internal PC timer that times out as it fills it's bit frame. Call LabVIEW
tech support for exact info. It has plagued several people running very
long programs. It may be related to your situation.
[email protected] wrote in message <7nn0qt$sl8$[email protected]>...
>Hi,
>
>I am having a problem with Labview shutting itself down after it is
>running for a long time. I am running a test that takes about 6 hours.
>I am confident that it isn't my code that is causing the failure since
>it just executes the same loop over and over with different permutations
>of data.
>
>I was just wondering if anyone else has experienced similar problems and
>if anyone has any suggestions?
>
>Thanks a lot
>J
enni
>
>
>Sent via Deja.com http://www.deja.com/
>Share what you know. Learn what you don't.

Labview Crashes after DLL call

HI All,
I am working on to write a wrapper to a dll. The call to dll works fine an returns appropriate values but as soon as i close the VI the LabVIEW dev environment crashes. Any help on avoiding the same. I went through a lot of posts and tried varing the types of data being sent to the dll but still it gets crashed.
the dll function I am using is of the prototype(with C type call convention)
int functionName(Struct *cfg, UCHAR dNumber, UCHAR hTYPE)
The UCHAR varables I am passing as Unsigned 8-bit Integers.
For the structure I have made a cluster and am passing with Adapt to Type and as Handles.
The DLL executes fine and the VI stops too, but as soon as i try to close the VI the dev environment crashes. Please help.
Thanks.
Solved!
Go to Solution.

While nathand is right about possible other errors, the Struct that you fail to tell anything about is a big flag pole for something that might be going wrong. Show us the C header declaring the structure and function and attach the VI you created (please no BMP or other image! They do say a picture says more than thousend words, but in the case of a LabVIEW diagram a picture is not enough to show all aspects of a VI, especially things like how the Call Library Node is configured!)
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

FCP7 crashes after long log and transfer L&T

In FCP7 it seems that I can L&T 60 minutes and even a bit longer with no problem. But every time I have footage that is 1.5 hours FCP crashes at the very end of the transfer. The file is created, I can see the 100+ gig file in the capture scratch folder, but it's not readable. I have to capture the file in 2 segments, which really stinks when syncing 2 or 3 or more cameras. Any idea what's going on here?
Thanks,
Eric

Have you tried resetting your fcp preferences? Digital Rebellion's Preference Manager is the best tool for doing this in my opinion.
https://discussions.apple.com/docs/DOC-2491
Have you loaded or installed any software recently or done any software updates?

LabVIEW crashes after VI (calls DLL to post Windows Msg) exits

I built a DLL in Visual C++ and I use LabVIEW 7.1 to call it (using the Call Library function).
When I run the LabVIEW VI without the 'post windows message' functionality in the DLL, it works fine and exits LabVIEW without a problem. If the DLL posts a message, and the code from the link below is used to catch the meassage, the VI appears to have executed and exit correctly, allowing other VIs to be run, etc, but when the VI is closed, LabVIEW stops responding. If it is the only VI open, then it closes leaving the LabVIEW window minimized (and unresponsive) in the Taskbar. Both DLLs successfully detached from LV before the VI stops running.
http://sine.ni.com/apps/we/niepd_web_display.DISPLAY_EPD4?p_guid=B45EACE3E7AC56A4E034080020E74861&p_node=DZ52071&p_submitted=N&p_rank=&p_answer=&p_source=External

Hi,
can you post your code here so we can try to reproduce it?
It sounds as if the handles aren't being released in the right order. i.e. LabVIEW will hold onto a DLL until the vi using it goes out of memory.
I think from your description you have a DLL which posts a message, and then you're using the example code which was written for LabVIEW 5.0 to read that windows message?
What message are you sending?
When you say the DLL has detached, is that process detach or thread detach?
What version of LabVIEW are you using?
What operating system?
What version of Visual C++?
Thanks
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer

My compiled program crashes after first run (LabVIEW 2009)

I have a compiled program created with LabVIEW 2009 that on the first run after the computer is re-booted will work fine but after shutting down the program it will not run properly.
The program uses a compiled launcher to dynamically activate a set of VI's containing Queue Driven State Machines (QDSM). On subsequent program starts the launcher module comes up fine and its progress bar shows that it is launching each of the VI's. Once the launcher is complete it removes itself from memory leaving the dynamically launched VI's running. The subsequent launches which fail the main user interface VI pops up barely long enough for the observer to see (if at all) then shuts down. The program is then gone from memory as far as I can tell. There are no processes in memory or anything.
Additionally, the when I try to run the installed version of the exe on a computer that has the 2009 development environment installed I get this behavior consistently with a successful run even once.
In both cases my program does not throw any errors (which are logged) nor does the runtime engine generate any that I can see. Also, when I run my program in the development environment the program does not behave this way. It has no problems at all.
I have used this style of architecture before in LV8.6 with out any problems. Can anyone suggest some possible solutions or even some debugging tips? I have never had a problem that I could not duplicate in the development environment so I am unsure how begin attacking my issue.
Thanks for any help.
Jason
Wire Warrior
Behold the power of LabVIEW as my army of Roomba minions streaks across the floor!
Solved!
Go to Solution.

I have solved the problem I think (at least as far as testing to this point has revealed). After I added in the ability to log the states passed to the QDSM's, I was able to determine that the program was "crashing" after I dynamically closed the front panel of the launcher. My program was designed to close the front panel of the launcher then pop-up the front panel of the main UI. My EXE is built on to contain the launcher with my other QDSM files being maintained externally in specific directories. What appeared to be happening is that when the launcher closed its front panel and before the UI opened up the run-time engine would decide since there were no windows open it would close itself down. This is my supposition about what may be happening any way. I modified my code to changed the launcher window to hidden and delay for 1/2 a second to give the main UI a chance to start fully running. This fixed the problem, or at least worked around it. If someone out there can explain to me exactly what is happening I sure would appreciate it.
Thanks for all the help those of you who responded. Your advice was very beneficial and certainly led me to a resolution faster.
Jason
Wire Warrior
Behold the power of LabVIEW as my army of Roomba minions streaks across the floor!

After update to Firefox 15 it crashes after javascript call window.close();opener.alert('test');. Is this working as intended or is it a bug?

After update to Firefox 15 it crashes after javascript call from a popup window.close();opener.alert('test');. Is this working as intended or is it a bug?

According to the pages linked to the crash ID, there is a bug report on this.
Does the crash occur as soon as you run those two lines of code, or after dismissing the alert()?
If this is your application, why are you running script commands after calling window.close()? Could you avoid the problem by using an approach like this:
 window.setTimeout(function(){opener.alert('test'},250);
window.close();

Labview Program always crashs after a few hour' work

My Labview Program always crashs after a few hour' work. The error report is:
#Date: 2014年7月30日 4:27:27
#OSName: Windows 7 Ultimate
#OSVers: 6.1
#OSBuild: 7600
#AppName:
#Version: 12.0 32-bit
#AppKind: AppLib
#AppModDate: 07/29/2014 20:13 GMT
#LabVIEW Base Address: 0x30000000
<DEBUG_OUTPUT>
2014/7/30 8:34:11.006
DAbort 0xF50EFD7B:
c:\builds\penguin\labview\components\mgcore\trunk\12.0\source\MemoryManager.cpp(1104) : DAbort 0xF50EFD7B:
minidump id: 6ebe0400-78d2-41e3-b2fd-858c21e3567b
$Id: //labview/components/mgcore/trunk/12.0/source/MemoryManager.cpp#13 $
</DEBUG_OUTPUT>
0x30076B23 - lvrt <unknown> + 0
0x307D1F90 - lvrt <unknown> + 0
0x30605C66 - lvrt <unknown> + 0
0x6C42A045 - nivissvc <unknown> + 0
0x075A1F00 - nivision <unknown> + 0
0x03B0577A - <unknown> <unknown> + 0
0xE5BA0800 - <unknown> <unknown> + 0
Who knows what had happened? Thank you for your help.

Thank you for your reply.
I don't build array continuously. I just build a few queues. I am sorry the program is too large to show it to you. I have read the dump file. It seems like memory overflow. Do you think so? But it seems like there is no chance for memory overflow in Labview. The dump file is as below:
Microsoft (R) Windows Debugger Version 6.3.9600.17029 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\LabVIEW Data\LVInternalReports\1.0.0.1\51437f73-aab6-4097-b7e1-3fee8a74e4dd\6ebe0400-78d2-41e3-b2fd-858c21e3567b.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available
************* Symbol Path validation summary **************
Response Time (ms) Location
OK C:\Program Files (x86)\Symbols
Symbol search path is: C:\Program Files (x86)\Symbols
Executable search path is:
Windows 7 Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
Machine Name:
Debug session time: Wed Jul 30 08:34:10.000 2014 (UTC + 8:00)
System Uptime: not available
Process Uptime: 0 days 4:06:44.000
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(dfc.4b8): Unknown exception - code 00000002 (first/second chance not available)
*** WARNING: Unable to verify timestamp for ntdll.dll
*** ERROR: Module load completed but symbols could not be loaded for ntdll.dll
*** WARNING: Unable to verify timestamp for kernel32.dll
*** ERROR: Module load completed but symbols could not be loaded for kernel32.dll
eax=13dbec20 ebx=13dbe550 ecx=00000008 edx=00000008 esi=00000003 edi=13dbe570
eip=77b564f4 esp=13dbe500 ebp=13dbe59c iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
ntdll+0x464f4:
77b564f4 c3 ret

Diadem 9 crashes after installing LabView 8.6

Hello,
I'm searching for a solution to fix a problem that occurred on Diadem 9.0 after installation of LabView 8.6.
The software was working fine until I've installed LabView. Since that time it crashes after few seconds I've already uninstalled it and installed it new, no progress...
Does anybody know what's the problem and how to fix it?
Thanks in advance,
Regards,
Paul
Solved!
Go to Solution.

Hello Paul and Otmar,
I had a similar problem a few month ago:
While installing LabVIEW 8.6, an actual NI-DAQmx driver was installed too. Please double-check the installed version. I guess, that it is something around NI-DAQmx 8.7. You will find this information in your "Measurement & Automation Explorer (MAX)" (Start -> Programms -> National Instruments). In MAX, please browse to 'My Computer -> Software -> NI-DAQmx'.
Please click on this item and you will get on the right side the installed version.
Unfortunately, the latest supported driver version of DIAdem 9.1 is NI-DAQmx 8.1. This information can be found here:
http://digital.ni.com/public.nsf/allkb/53BA46C79DE2786686257249005619A5?OpenDocument
If you have installed a later version of DAQmx, please consider to upgrade your DIAdem to a newer version. If this is not possible, you have to deinstall the actual DAQmx-driver and install DAQmx 8.1. This one can be found here:
http://joule.ni.com/nidu/cds/view/p/id/319/lang/en
I hope, that this helped you.
Best regards and have a great weekend
Message Edited by MarianMO on 04-17-2009 02:46 PM
MarianO

V27 crashed after testing v32 in iOS7/iOS6

Hi,
We are considering to upgrade our app with v32 from v27. I got one problem when testing with v32.
Basically v27 version (downloading from itunes) crashed after I installed and tested v32 from local Mac computer. I have tried on iOS7 and iOS6. It did the same thing. v27 (our live one) just crashed on both systems after I have installed and tested the v32 test version.
I have tried to delete the app and reinstall it again, hard restart the ipad and login as another account in the ipad, none of them worked out.
Do you know anything about this? Please help us! Any help would be appreciated!
Thanks
Jiping

This is because the keychain information was updated when you installed the v32 app was installed, but now that you have v27 installed again it can't handle that updated data. Let me check with the test team to see if there's a way to clear that out without clearing the entire iPad.
Neil

Quicktime Broadcaster crashes after a few seconds

Hi
This will probably be all too vague for a good answer but thought I'd ask anyway...
Does have experience of Quicktime Broadcaster being unstable? I've tried using it with a USB webcam (logitech pro 9000) device that works fine with other apps on the Mac and an XP laptop but once broadcasting (to Darwin STreaming Server on another machine) QT Broadcaster crashes after a few seconds or minutes, or when you try to use another application. Looks like memory conflicts but it worked for much longer periods of time earlier this year but after the usual upgrades to 10.4.xx (to 10.4.11) it's become unuseable.
I was wondering if anyone knew if upgrading to 10.5.xx would sort the problem out?
Any help or pointers much appreciated.
Bill

I'm using the latest version of QT Broadcaster (1.5.2) on a MacBook running OS 10.5.6, using an old external iSight camera for the video input, and I can broadcast for hours without problems. I would recommend an update to Leopard. I might also suggest that you perform a hardware test and check your DRAM, just to be on the safe side.

Ti 17 crashes after Update 10.4.3

Hi
As I say in the title, my 17' crashes after update10.4.3. I' have entirely erase the disk and reinstall the system 10.4. Updating with 10.4.3 : same issue. Erasing all the disk an reinstalling (with 2 partitions). Updating with 10.4.1 : ok. Updating with 10.4.2 : ok. Updating with 10.4.3 : kernel panic at startup. In fact, on the grey screen, the wheel is making a lot of round (more than 50) and the system crashes with kernel panic. With the other partition (10.4), i've a look to log files. No information about the crash. Trying to reinstall all : same issue. Resettting PRAM, NVRAM, fsck -yf, repairing disk and permissions and diskwarrior : same issue. I suspect video drivers, I replace new drivers by the old : same issue. Suspecting Ram and using Hardware test : all is good even the RAM in long test.
So i decided to install 10.3. The last owner had said to me that he can be an upgarde over 10.3.5. He was right. Updating to 10.3.9 (combo) causes a crash with kernel panic but I've a message... To long to be coping here. But it star with
Unresolved kernel trap (cpu 0) : 0X700 - Program DAR=0x0..02BB05C etc.
No mention of an extension or known program except perhaps
root : xnu/xnu-517.12.7.obj~1/RELEASE_PPC
Please help me. That's 2 days that I'm working on it without any result and I'm desesperate.
PS This is the first mac which resists to all my efforts

You may not be able to install 10.3 on an Aluminum 17" Powerbook depending on which operating system it came with:
http://docs.info.apple.com/article.html?artnum=25517
So figuring out which 17" Powerbook you have is essential to figuring out if the reason why 10.3 won't install is because of the built-in hardware limitation, or a hardware issue with the computer. Use the article I provided together with article 25517 above to figure that out. If the machine came with 10.3, you have to use the Powerbook G4 installer disk marked 10.3. If it came with 10.2.8 or earlier you have to use the black 10.3 installer disks with the white and gray X logo that do not say Update unless the machine was released between October 8th, 2003 and the date that 10.3 was included with all 17" Powerbooks.

Premier Pro CC and Media Encoder crashing on long file export.

Please forgive the length of this inquiry. But it is complicated and has a lot of variables.
I have an hour long mixed format timeline both Red 3K footage and Black Magic ProRes 1080P footage that I want to make a DVD from and it takes forever and crashes half way through. I have tried doing it every way possible and the only way I was able to get even a partial export was using the "MPEG 2 DVD" export option in Premier CC. It goes fast at first telling me it will take about 2 hours but even though it starts quickly doing about 15 fps it slows down to less than 1 fps and finally just stops and crashes my Cuda Core enabled Macbook Pro Laptop.
I really don't know who to ask about this since there are so many different variables. I never had a problem like this on my MBP with PP6 on a 4K timeline exporting to DVD or Blue Ray or to H-264 or Even Prores. But I wasn't mixing formats either. But on this project the first 20-30 minutes of footage goes through fine in a couple of hours but something seems to be bogging down the system on longer projects. My work around was to break the project up into multiple exports and combining them on the DVD timeline but I can't do this on every project. I thought maybe it was a corrupted clip somewhere in the timeline but when I broke the timeline up into several parts I had no problems.
I did notice a dramatic variance in the time it took to export footage based on the sequence settings. A one minute timeline comprised Red 3K footage and ProRes 1080P footage Here are some sample export results:
From a Red raw 3K timeline 2880x1620 with 1080P Prores footage upscaled 150%)
to .m2v Mpeg 2 720x480 format 1:48 Minutes ***
to .mov Prores 422HQ 1080P 22 Minutes
to .mov H.264 1080P 22 Minutes
to .m2v Mpeg 2 1080P 22 Minutes
From a 1080P timeline Prores footage at 100% (Red footage downscaled to 67%)
to .m2v Mpeg 2 720x480 format 13 Minutes
to .mov Prores 422HQ 1080P 13 Minutes
to .mov H.264 1080P 14 Minutes
to .m2v Mpeg 2 1080P 14 Minutes
Since I am going to DVD, I chose the fastest option Red to m2v Mpeg 2 720x480 format which only took 1:48 per minute. Why? I have no idea. Maybe someone here knows the answer. But again these numbers are for a ONE MINUTE clip when I tried to convert the whole hour timeline to the 720x480.m2v DVD File the Red timeline froze my computer after several hours even though I had set sleep mode to “Never” and turned the display off manually and I had to convert it in multiple chunks. In 20-30 minute chunks it did go fast about 1:48 per minute like the test indicated. But I would like to be able to convert the whole hour and not to have to try to stitch the clips together in my DVD authoring program.
I don’t want to have to avoid using multiple formats on the same timeline or waste time transcoding everything to the same format.
Can anyone give me any suggestions as to why the computer is crashing or bogging down in long exports and what timeline settings I should be using?
I have plenty of room on my Scratch Disk and 8 Gig of RAM and according to my Activity Monitor during the export process have about 800 Meg of System Memory during export but the CPU Usage is 98% and in my Activity Monitor I see under “Process Name” ImporterRedServer flashing up at the top of the list about every second during export.
Why .720x480 mpeg DVD setting is so much faster than all the other export codecs?
And if there are any other settings I can use to get higher speed exports in HD? 14x1 seems a little slow especially since every time it crashes I have to start over.

Hi,
Since a long time I did not encounter the crash of Media encoder with
long file export.
But I take care of a lot of details before the export :
- clean up Media cache and Media Cache Files within PP CS6 and/or CC,
- delete all render files with Preview Files,
- rendering of sequences until the rendering is completed,
- PP CS6 and/or Pp CC opened during export to AME and/or Encore CS6,
I guessed to leave Adobe but this company remains the last with a
serious authoring software (Encore CS 6).
I tested :
- Avid Media Composer, Final Cut Pro X, both are very good software but
no really authoring software for these video editing softs.
Th only way is to "flood" Adobe with "bug reports" and "wish forms"
which are not very easy to use.
And also to call the Adobe support day by day until they send they
escalate the bug.
Le 16/05/2014 16:51, alainmaiki a écrit :
>
 Premier Pro CC and Media Encoder crashing on long file export.
created by alainmaiki <https://forums.adobe.com/people/alainmaiki> in
/Premiere Pro/ - View the full discussion
<https://forums.adobe.com/message/6384665#6384665>

Photoshop CS5 crashing after 5 mins??

So after installing Lion, photoshop is continually crashing after a couple of minutes of using it and I have no idea what the problem is? Is it possibly a memory issue - as this rarely happened in Snow Leopard, especially during CPU intensive sessions?? i'm just at a loss and am panicking..
Can anyone help please!?
thanks!
Steven
crash report:
Process: Adobe Photoshop CS5 [1396]
Path: /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/MacOS/Adobe Photoshop CS5
Identifier: com.adobe.Photoshop
Version: 12.0.4 (12.0.4x20110407.r.1265] [12.0.4)
Code Type: X86-64 (Native)
Parent Process: launchd [143]
Date/Time: 2011-07-24 17:44:56.819 +0800
OS Version: Mac OS X 10.7 (11A511)
Report Version: 9
Interval Since Last Report: 57144 sec
Crashes Since Last Report: 6
Per-App Interval Since Last Report: 14692 sec
Per-App Crashes Since Last Report: 5
Anonymous UUID: 78708BE6-D099-4B05-A9E8-25A6780044A6
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0xffffffffffffffff
VM Regions Near 0xffffffffffffffff:
--> shared memory 00007fffffe00000-00007fffffe02000 [ 8K] r-x/r-x SM=SHM
Application Specific Information:
objc[1396]: garbage collection is OFF
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.adobe.Photoshop 0x00000001001a4b7c 0x100000000 + 1723260
1 MultiProcessor Support 0x000000010d715e40 MPGetInterLevelMipMapPixelBlock(unsigned char*, int, int, int, int, int, int, int, int, int, int, int, int, BrushMipMap**) + 278
2 com.adobe.Photoshop 0x0000000100fcb02d AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 13560721
3 com.adobe.Photoshop 0x0000000100fcbf93 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 13564663
4 com.adobe.Photoshop 0x0000000100fcc42f AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 13565843
5 com.adobe.Photoshop 0x0000000100fc83d1 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 13549365
6 com.adobe.Photoshop 0x0000000100fea91d AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 13689985
7 com.adobe.Photoshop 0x0000000100fead4d AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 13691057
8 com.adobe.Photoshop 0x0000000100feaf30 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 13691540
9 com.adobe.Photoshop 0x0000000100fe5ac7 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 13669931
10 com.adobe.Photoshop 0x0000000100fe7957 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 13677755
11 com.adobe.Photoshop 0x0000000100688bb9 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 3852061
12 com.adobe.Photoshop 0x0000000100689982 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 3855590
13 com.adobe.Photoshop 0x0000000100689e3a AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 3856798
14 com.adobe.Photoshop 0x000000010068a2ad AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 3857937
15 com.adobe.Photoshop 0x00000001006887a7 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 3851019
16 com.adobe.Photoshop 0x000000010068a87f AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 3859427
17 com.adobe.Photoshop 0x0000000100ff16d7 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 13718075
18 com.adobe.Photoshop 0x0000000100ff1797 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 13718267
19 com.adobe.Photoshop 0x00000001009ce4c8 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 7282732
20 com.adobe.Photoshop 0x0000000100546e2f AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 2533779
21 com.adobe.Photoshop 0x00000001000c4d32 0x100000000 + 806194
22 com.adobe.Photoshop 0x00000001000c4be9 0x100000000 + 805865
23 com.adobe.Photoshop 0x00000001000c4be9 0x100000000 + 805865
24 com.adobe.Photoshop 0x00000001000c4be9 0x100000000 + 805865
25 com.adobe.Photoshop 0x00000001000c4be9 0x100000000 + 805865
26 com.adobe.Photoshop 0x00000001000c4be9 0x100000000 + 805865
27 com.adobe.Photoshop 0x00000001000c4be9 0x100000000 + 805865
28 com.adobe.Photoshop 0x00000001000c4be9 0x100000000 + 805865
29 com.adobe.Photoshop 0x00000001000c9fb9 0x100000000 + 827321
30 com.adobe.Photoshop 0x0000000100cdf3f8 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 10497884
31 com.adobe.Photoshop 0x0000000100cdb13e AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 10480802
32 com.adobe.Photoshop 0x00000001000677e1 0x100000000 + 423905
33 com.adobe.Photoshop 0x00000001006b099a AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 4015358
34 com.adobe.Photoshop 0x00000001000679e4 0x100000000 + 424420
35 com.adobe.Photoshop 0x0000000100065f1b 0x100000000 + 417563
36 com.adobe.Photoshop 0x00000001012dba1e AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 16774530
37 com.adobe.Photoshop 0x00000001012d4411 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 16744309
38 com.apple.CoreFoundation 0x00007fff868d811d -[NSObject performSelector:withObject:] + 61
39 com.adobe.Photoshop 0x00000001012d4f33 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 16747159
40 com.apple.AppKit 0x00007fff897b916a forwardMethod + 129
41 com.apple.CoreFoundation 0x00007fff868d811d -[NSObject performSelector:withObject:] + 61
42 com.apple.AppKit 0x00007fff897b916a forwardMethod + 129
43 com.apple.AppKit 0x00007fff897b366e -[NSWindow sendEvent:] + 6280
44 com.adobe.owl 0x000000010368af55 OWLRemoveObjCExceptionCallback + 617
45 com.adobe.owl 0x000000010368cfa4 OWLRemoveObjCExceptionCallback + 8888
46 com.apple.AppKit 0x00007fff8974bf19 -[NSApplication sendEvent:] + 5665
47 com.adobe.Photoshop 0x00000001012e242e AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 16801682
48 com.adobe.Photoshop 0x00000001012e1be1 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 16799557
49 com.apple.AppKit 0x00007fff896e242b -[NSApplication run] + 548
50 com.adobe.Photoshop 0x00000001012e04a4 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 16793608
51 com.adobe.Photoshop 0x00000001012e0f01 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 16796261
52 com.adobe.Photoshop 0x00000001000682e6 0x100000000 + 426726
53 com.adobe.Photoshop 0x00000001002371f1 0x100000000 + 2322929
54 com.adobe.Photoshop 0x0000000100237281 0x100000000 + 2323073
55 com.adobe.Photoshop 0x00000001000022f4 0x100000000 + 8948
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff8c6627e6 kevent + 10
1 libdispatch.dylib 0x00007fff840ed60e _dispatch_mgr_invoke + 923
2 libdispatch.dylib 0x00007fff840ec19e _dispatch_mgr_thread + 54
Thread 2:
0 libsystem_kernel.dylib 0x00007fff8c661bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8b0ca274 _pthread_cond_wait + 840
2 com.adobe.amt.services 0x0000000108723c53 AMTConditionLock::LockWhenCondition(int) + 37
3 com.adobe.amt.services 0x000000010871ccce _AMTThreadedPCDService::PCDThreadWorker(_AMTThreadedPCDService*) + 92
4 com.adobe.amt.services 0x0000000108723cbe AMTThread::Worker(void*) + 28
5 libsystem_c.dylib 0x00007fff8b0c68bf _pthread_start + 335
6 libsystem_c.dylib 0x00007fff8b0c9b75 thread_start + 13
Thread 3:
0 libsystem_kernel.dylib 0x00007fff8c6606ce semaphore_timedwait_trap + 10
1 com.apple.CoreServices.CarbonCore 0x00007fff88b7e96a MPWaitOnSemaphore + 77
2 MultiProcessor Support 0x000000010d720b93 ThreadFunction(void*) + 69
3 com.apple.CoreServices.CarbonCore 0x00007fff88b7f3e2 PrivateMPEntryPoint + 58
4 libsystem_c.dylib 0x00007fff8b0c68bf _pthread_start + 335
5 libsystem_c.dylib 0x00007fff8b0c9b75 thread_start + 13
Thread 4:
0 libsystem_kernel.dylib 0x00007fff8c661bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8b0ca274 _pthread_cond_wait + 840
2 com.apple.CoreServices.CarbonCore 0x00007fff88ba715a TSWaitOnCondition + 106
3 com.apple.CoreServices.CarbonCore 0x00007fff88b39912 TSWaitOnConditionTimedRelative + 127
4 com.apple.CoreServices.CarbonCore 0x00007fff88b7e57d MPWaitOnQueue + 181
5 AdobeACE 0x000000010598b18d 0x105951000 + 237965
6 AdobeACE 0x000000010598ab3a 0x105951000 + 236346
7 com.apple.CoreServices.CarbonCore 0x00007fff88b7f3e2 PrivateMPEntryPoint + 58
8 libsystem_c.dylib 0x00007fff8b0c68bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff8b0c9b75 thread_start + 13
Thread 5:
0 libsystem_kernel.dylib 0x00007fff8c661bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8b0ca274 _pthread_cond_wait + 840
2 com.apple.CoreServices.CarbonCore 0x00007fff88ba715a TSWaitOnCondition + 106
3 com.apple.CoreServices.CarbonCore 0x00007fff88b39912 TSWaitOnConditionTimedRelative + 127
4 com.apple.CoreServices.CarbonCore 0x00007fff88b7e57d MPWaitOnQueue + 181
5 AdobeACE 0x000000010598b18d 0x105951000 + 237965
6 AdobeACE 0x000000010598ab3a 0x105951000 + 236346
7 com.apple.CoreServices.CarbonCore 0x00007fff88b7f3e2 PrivateMPEntryPoint + 58
8 libsystem_c.dylib 0x00007fff8b0c68bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff8b0c9b75 thread_start + 13
Thread 6:
0 libsystem_kernel.dylib 0x00007fff8c661bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8b0ca274 _pthread_cond_wait + 840
2 com.apple.CoreServices.CarbonCore 0x00007fff88ba715a TSWaitOnCondition + 106
3 com.apple.CoreServices.CarbonCore 0x00007fff88b39912 TSWaitOnConditionTimedRelative + 127
4 com.apple.CoreServices.CarbonCore 0x00007fff88b7e57d MPWaitOnQueue + 181
5 AdobeACE 0x000000010598b18d 0x105951000 + 237965
6 AdobeACE 0x000000010598ab3a 0x105951000 + 236346
7 com.apple.CoreServices.CarbonCore 0x00007fff88b7f3e2 PrivateMPEntryPoint + 58
8 libsystem_c.dylib 0x00007fff8b0c68bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff8b0c9b75 thread_start + 13
Thread 7:
0 libsystem_kernel.dylib 0x00007fff8c661e42 __semwait_signal + 10
1 libsystem_c.dylib 0x00007fff8b07cdea nanosleep + 164
2 com.adobe.PSAutomate 0x0000000122682e4b ScObjects::Thread::sleep(unsigned int) + 59
3 com.adobe.PSAutomate 0x0000000122664d83 ScObjects::BridgeTalkThread::run() + 163
4 com.adobe.PSAutomate 0x0000000122682f46 ScObjects::Thread::go(void*) + 166
5 libsystem_c.dylib 0x00007fff8b0c68bf _pthread_start + 335
6 libsystem_c.dylib 0x00007fff8b0c9b75 thread_start + 13
Thread 8:
0 libsystem_kernel.dylib 0x00007fff8c661bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8b0ca274 _pthread_cond_wait + 840
2 com.adobe.adobeswfl 0x000000013368789d APXGetHostAPI + 2465805
3 com.adobe.adobeswfl 0x00000001334405e9 APXGetHostAPI + 77145
4 com.adobe.adobeswfl 0x00000001336879b1 APXGetHostAPI + 2466081
5 com.adobe.adobeswfl 0x0000000133687d1a APXGetHostAPI + 2466954
6 com.adobe.adobeswfl 0x0000000133687e49 APXGetHostAPI + 2467257
7 libsystem_c.dylib 0x00007fff8b0c68bf _pthread_start + 335
8 libsystem_c.dylib 0x00007fff8b0c9b75 thread_start + 13
Thread 9:
0 libsystem_kernel.dylib 0x00007fff8c661bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8b0ca274 _pthread_cond_wait + 840
2 com.adobe.adobeswfl 0x000000013368789d APXGetHostAPI + 2465805
3 com.adobe.adobeswfl 0x00000001334405e9 APXGetHostAPI + 77145
4 com.adobe.adobeswfl 0x00000001336879b1 APXGetHostAPI + 2466081
5 com.adobe.adobeswfl 0x0000000133687d1a APXGetHostAPI + 2466954
6 com.adobe.adobeswfl 0x0000000133687e49 APXGetHostAPI + 2467257
7 libsystem_c.dylib 0x00007fff8b0c68bf _pthread_start + 335
8 libsystem_c.dylib 0x00007fff8b0c9b75 thread_start + 13
Thread 10:
0 libsystem_kernel.dylib 0x00007fff8c661bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8b0ca274 _pthread_cond_wait + 840
2 com.adobe.adobeswfl 0x000000013368789d APXGetHostAPI + 2465805
3 com.adobe.adobeswfl 0x00000001334405e9 APXGetHostAPI + 77145
4 com.adobe.adobeswfl 0x00000001336879b1 APXGetHostAPI + 2466081
5 com.adobe.adobeswfl 0x0000000133687d1a APXGetHostAPI + 2466954
6 com.adobe.adobeswfl 0x0000000133687e49 APXGetHostAPI + 2467257
7 libsystem_c.dylib 0x00007fff8b0c68bf _pthread_start + 335
8 libsystem_c.dylib 0x00007fff8b0c9b75 thread_start + 13
Thread 11:
0 libsystem_kernel.dylib 0x00007fff8c661bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8b0ca274 _pthread_cond_wait + 840
2 com.adobe.adobeswfl 0x000000013368789d APXGetHostAPI + 2465805
3 com.adobe.adobeswfl 0x00000001334405e9 APXGetHostAPI + 77145
4 com.adobe.adobeswfl 0x00000001336879b1 APXGetHostAPI + 2466081
5 com.adobe.adobeswfl 0x0000000133687d1a APXGetHostAPI + 2466954
6 com.adobe.adobeswfl 0x0000000133687e49 APXGetHostAPI + 2467257
7 libsystem_c.dylib 0x00007fff8b0c68bf _pthread_start + 335
8 libsystem_c.dylib 0x00007fff8b0c9b75 thread_start + 13
Thread 12:
0 libsystem_kernel.dylib 0x00007fff8c66067a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8c65fd71 mach_msg + 73
2 com.apple.CoreFoundation 0x00007fff8687529c __CFRunLoopServiceMachPort + 188
3 com.apple.CoreFoundation 0x00007fff8687da04 __CFRunLoopRun + 1204
4 com.apple.CoreFoundation 0x00007fff8687d216 CFRunLoopRunSpecific + 230
5 com.apple.CoreMediaIO 0x00007fff86a85541 CMIO::DAL::RunLoop::OwnThread(void*) + 159
6 com.apple.CoreMediaIO 0x00007fff86a7b6b2 CAPThread::Entry(CAPThread*) + 98
7 libsystem_c.dylib 0x00007fff8b0c68bf _pthread_start + 335
8 libsystem_c.dylib 0x00007fff8b0c9b75 thread_start + 13
Thread 13:
0 libsystem_kernel.dylib 0x00007fff8c661bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8b0ca2a6 _pthread_cond_wait + 890
2 com.adobe.adobeswfl 0x0000000133687869 APXGetHostAPI + 2465753
3 com.adobe.adobeswfl 0x00000001336a40ec APXGetHostAPI + 2582620
4 com.adobe.adobeswfl 0x00000001336879b1 APXGetHostAPI + 2466081
5 com.adobe.adobeswfl 0x0000000133687d1a APXGetHostAPI + 2466954
6 com.adobe.adobeswfl 0x0000000133687e49 APXGetHostAPI + 2467257
7 libsystem_c.dylib 0x00007fff8b0c68bf _pthread_start + 335
8 libsystem_c.dylib 0x00007fff8b0c9b75 thread_start + 13
Thread 14:
0 libsystem_kernel.dylib 0x00007fff8c661bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8b0ca2a6 _pthread_cond_wait + 890
2 com.adobe.adobeswfl 0x0000000133687869 APXGetHostAPI + 2465753
3 com.adobe.adobeswfl 0x0000000133821e6f APXGetHostAPI + 4146655
4 com.adobe.adobeswfl 0x00000001336879b1 APXGetHostAPI + 2466081
5 com.adobe.adobeswfl 0x0000000133687d1a APXGetHostAPI + 2466954
6 com.adobe.adobeswfl 0x0000000133687e49 APXGetHostAPI + 2467257
7 libsystem_c.dylib 0x00007fff8b0c68bf _pthread_start + 335
8 libsystem_c.dylib 0x00007fff8b0c9b75 thread_start + 13
Thread 15:
0 libsystem_kernel.dylib 0x00007fff8c661d7a __recvfrom + 10
1 ServiceManager-Launcher.dylib 0x0000000135d13982 Invoke + 54020
2 ServiceManager-Launcher.dylib 0x0000000135d12adf Invoke + 50273
3 ServiceManager-Launcher.dylib 0x0000000135d11b26 Invoke + 46248
4 ServiceManager-Launcher.dylib 0x0000000135d11b81 Invoke + 46339
5 ServiceManager-Launcher.dylib 0x0000000135d11c02 Invoke + 46468
6 ServiceManager-Launcher.dylib 0x0000000135d0c30d Invoke + 23695
7 ServiceManager-Launcher.dylib 0x0000000135d0c4a6 Invoke + 24104
8 ServiceManager-Launcher.dylib 0x0000000135d0cf2f Invoke + 26801
9 ServiceManager-Launcher.dylib 0x0000000135d0d01d Invoke + 27039
10 ServiceManager-Launcher.dylib 0x0000000135d1031f Invoke + 40097
11 ServiceManager-Launcher.dylib 0x0000000135d105c5 Invoke + 40775
12 ServiceManager-Launcher.dylib 0x0000000135d10b84 Invoke + 42246
13 ServiceManager-Launcher.dylib 0x0000000135d10d71 Invoke + 42739
14 ServiceManager-Launcher.dylib 0x0000000135d02daf Login + 1773
15 ServiceManager-Launcher.dylib 0x0000000135d04295 Login + 7123
16 ServiceManager-Launcher.dylib 0x0000000135d112a8 Invoke + 44074
17 ServiceManager-Launcher.dylib 0x0000000135d136c1 Invoke + 53315
18 libsystem_c.dylib 0x00007fff8b0c68bf _pthread_start + 335
19 libsystem_c.dylib 0x00007fff8b0c9b75 thread_start + 13
Thread 16:
0 libsystem_kernel.dylib 0x00007fff8c661bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8b0ca274 _pthread_cond_wait + 840
2 libtbb.dylib 0x0000000106bf822c tbb::internal::GenericScheduler::wait_while_pool_is_empty() + 92
3 libtbb.dylib 0x0000000106c02b84 tbb::internal::CustomScheduler<tbb::internal::IntelSchedulerTraits>:: wait_for_all(tbb::task&, tbb::task*) + 1858
4 libtbb.dylib 0x0000000106bfae3a tbb::internal::GenericScheduler::worker_routine(void*) + 632
5 libsystem_c.dylib 0x00007fff8b0c68bf _pthread_start + 335
6 libsystem_c.dylib 0x00007fff8b0c9b75 thread_start + 13
Thread 17:
0 libsystem_kernel.dylib 0x00007fff8c661bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8b0ca274 _pthread_cond_wait + 840
2 libtbb.dylib 0x0000000106bf822c tbb::internal::GenericScheduler::wait_while_pool_is_empty() + 92
3 libtbb.dylib 0x0000000106c02b84 tbb::internal::CustomScheduler<tbb::internal::IntelSchedulerTraits>:: wait_for_all(tbb::task&, tbb::task*) + 1858
4 libtbb.dylib 0x0000000106bfae3a tbb::internal::GenericScheduler::worker_routine(void*) + 632
5 libsystem_c.dylib 0x00007fff8b0c68bf _pthread_start + 335
6 libsystem_c.dylib 0x00007fff8b0c9b75 thread_start + 13
Thread 18:
0 libsystem_kernel.dylib 0x00007fff8c661bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8b0ca274 _pthread_cond_wait + 840
2 libtbb.dylib 0x0000000106bf822c tbb::internal::GenericScheduler::wait_while_pool_is_empty() + 92
3 libtbb.dylib 0x0000000106c02b84 tbb::internal::CustomScheduler<tbb::internal::IntelSchedulerTraits>:: wait_for_all(tbb::task&, tbb::task*) + 1858
4 libtbb.dylib 0x0000000106bfae3a tbb::internal::GenericScheduler::worker_routine(void*) + 632
5 libsystem_c.dylib 0x00007fff8b0c68bf _pthread_start + 335
6 libsystem_c.dylib 0x00007fff8b0c9b75 thread_start + 13
Thread 19:
0 libsystem_kernel.dylib 0x00007fff8c661bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8b0ca274 _pthread_cond_wait + 840
2 libtbb.dylib 0x0000000106bf822c tbb::internal::GenericScheduler::wait_while_pool_is_empty() + 92
3 libtbb.dylib 0x0000000106c02b84 tbb::internal::CustomScheduler<tbb::internal::IntelSchedulerTraits>:: wait_for_all(tbb::task&, tbb::task*) + 1858
4 libtbb.dylib 0x0000000106bfae3a tbb::internal::GenericScheduler::worker_routine(void*) + 632
5 libsystem_c.dylib 0x00007fff8b0c68bf _pthread_start + 335
6 libsystem_c.dylib 0x00007fff8b0c9b75 thread_start + 13
Thread 20:
0 libsystem_kernel.dylib 0x00007fff8c661bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8b0ca2a6 _pthread_cond_wait + 890
2 com.apple.CoreServices.CarbonCore 0x00007fff88b39930 TSWaitOnConditionTimedRelative + 157
3 com.apple.CoreServices.CarbonCore 0x00007fff88b39707 TSWaitOnSemaphoreCommon + 358
4 com.apple.CoreServices.CarbonCore 0x00007fff88b6ce96 AsyncFileThread(void*) + 219
5 libsystem_c.dylib 0x00007fff8b0c68bf _pthread_start + 335
6 libsystem_c.dylib 0x00007fff8b0c9b75 thread_start + 13
Thread 21:
0 libsystem_kernel.dylib 0x00007fff8c662192 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff8b0c8594 _pthread_wqthread + 758
2 libsystem_c.dylib 0x00007fff8b0c9b85 start_wqthread + 13
Thread 22:
0 libsystem_kernel.dylib 0x00007fff8c662192 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff8b0c8594 _pthread_wqthread + 758
2 libsystem_c.dylib 0x00007fff8b0c9b85 start_wqthread + 13
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000001 rbx: 0x00000000ffffffff rcx: 0x00000000000000aa rdx: 0x00000000000000b9
rdi: 0xffffffffffffffff rsi: 0x0000000000000000 rbp: 0x00007fff5fbfcbb0 rsp: 0x00007fff5fbfcb18
 r8: 0x0000000000000000 r9: 0x0000000000000002 r10: 0x0000000000000000 r11: 0x000000010d715d2a
r12: 0x000000010750f2ac r13: 0x00000000ff73ea7d r14: 0x0000000000000000 r15: 0x000000010750f2ac
rip: 0x00000001001a4b7c rfl: 0x0000000000010202 cr2: 0xffffffffffffffff
Logical CPU: 2
Binary Images:
 0x100000000 - 0x1026fbfff +com.adobe.Photoshop (12.0.4 - 12.0.4x20110407.r.1265] [12.0.4) <6BFE637D-7ADA-BD5C-F1C5-64AD4688D89D> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/MacOS/Adobe Photoshop CS5
 0x1032f4000 - 0x10336cfef +com.adobe.adobe_caps (adobe_caps 3.0.116.0 - 3.0.116.0) <4A355686-1451-B19A-0C55-DFE49FD2539E> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/adobe_caps.framework/Versions/A/adobe_cap s
 0x103382000 - 0x103389fff org.twain.dsm (1.9.4 - 1.9.4) <17E583BD-BFCC-366B-86C5-AB02D7257F60> /System/Library/Frameworks/TWAIN.framework/Versions/A/TWAIN
 0x103391000 - 0x1033a1ff8 +com.adobe.ahclientframework (1.5.0.30 - 1.5.0.30) <5D6FFC4E-7B81-3E8C-F0D4-66A3FA94A837> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/ahclient.framework/Versions/A/ahclient
 0x1033ac000 - 0x1033b2fff com.apple.agl (3.1.4 - AGL-3.1.4) <AB6F0403-0C4C-3FF2-B59E-2246E5F8F810> /System/Library/Frameworks/AGL.framework/Versions/A/AGL
 0x1033b9000 - 0x1035bffef +com.adobe.linguistic.LinguisticManager (5.0.0 - 11696) <499B4E7A-08BB-80FC-C220-D57D45CA424F> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/AdobeLinguistic.framework/Versions/3/Adob eLinguistic
 0x103652000 - 0x103800fef +com.adobe.owl (AdobeOwl version 3.0.93 - 3.0.93) <74CF40F6-B216-DB73-5C8F-FC5533220CD9> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/AdobeOwl.framework/Versions/A/AdobeOwl
 0x1038a2000 - 0x103cd2fef +AdobeMPS (??? - ???) <E541F5F1-21BB-D779-1475-B1553950E1B9> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/AdobeMPS.framework/Versions/A/AdobeMPS
 0x103e2c000 - 0x104157ff7 +AdobeAGM (??? - ???) <770E65CA-643B-CFEE-2BE1-F73D45B77D09> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/AdobeAGM.framework/Versions/A/AdobeAGM
 0x104224000 - 0x10454cfe7 +AdobeCoolType (??? - ???) <9979447D-9477-BC48-A84E-8A6A6AF380B5> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/AdobeCoolType.framework/Versions/A/AdobeC oolType
 0x1045e4000 - 0x104605ff7 +AdobeBIBUtils (??? - ???) <E0E813D7-0DEE-4BD6-599B-B1DE16008C3C> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/AdobeBIBUtils.framework/Versions/A/AdobeB IBUtils
 0x104612000 - 0x10463dff6 +AdobeAXE8SharedExpat (??? - ???) <7E809606-BF97-DB3A-E465-156446E56D00> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/AdobeAXE8SharedExpat.framework/Versions/A /AdobeAXE8SharedExpat
 0x10464f000 - 0x104793fef +WRServices (??? - ???) <76354373-F0BD-0BAF-6FC0-B96DBB371755> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/WRServices.framework/Versions/A/WRService s
 0x1047da000 - 0x10483ffff +aif_core (??? - ???) <28B07687-9957-7C0B-B221-1B849283C87A> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/aif_core.framework/Versions/A/aif_core
 0x10485b000 - 0x104871fff +data_flow (??? - ???) <81432128-C1BC-2E87-852E-2E4FBE63DEF3> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/data_flow.framework/Versions/A/data_flow
 0x104889000 - 0x10491ffff +image_flow (??? - ???) <83A775AD-5EFE-4EC1-4EE4-7A92C88D1B02> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/image_flow.framework/Versions/A/image_flo w
 0x104996000 - 0x1049b4fff +image_runtime (??? - ???) <F3EE4945-4348-A9BE-61AD-A546D0371C62> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/image_runtime.framework/Versions/A/image_ runtime
 0x1049d1000 - 0x104c00fff +aif_ogl (??? - ???) <0C2C2B20-688E-18BE-B33C-9B2A816A7E65> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/aif_ogl.framework/Versions/A/aif_ogl
 0x104cdf000 - 0x104d72fff +AdobeOwlCanvas (??? - ???) <EC667F6D-0BB6-03EA-41E8-624425B2BF4B> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/AdobeOwlCanvas.framework/Versions/A/Adobe OwlCanvas
 0x104d92000 - 0x1050dbfef +com.adobe.dvaui.framework (dvaui version 5.0.0 - 5.0.0.0) <023E0760-0223-AB5D-758C-2C5A052F6AF4> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/dvaui.framework/Versions/A/dvaui
 0x10526b000 - 0x1053edfe7 +com.adobe.dvacore.framework (dvacore version 5.0.0 - 5.0.0.0) <42077295-9026-D519-C057-35E07029D97B> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/dvacore.framework/Versions/A/dvacore
 0x10548f000 - 0x105807fff +com.adobe.dvaadameve.framework (dvaadameve version 5.0.0 - 5.0.0.0) <0E95A0DF-038A-CFF2-EC7B-BDB905CDF5C5> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/dvaadameve.framework/Versions/A/dvaadamev e
 0x105951000 - 0x105a66fff +AdobeACE (??? - ???) <C544307E-C1E6-FCA8-4D32-2EC0D5820BBD> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/AdobeACE.framework/Versions/A/AdobeACE
 0x105a8b000 - 0x105aa7fff +AdobeBIB (??? - ???) <EBA9513A-E3A2-10A8-35E9-B2A8DCDE10DD> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/AdobeBIB.framework/Versions/A/AdobeBIB
 0x105ab1000 - 0x105b1bff7 +com.adobe.amtlib (amtlib 3.0.0.64 - 3.0.0.64) <6B2F73C2-10AB-08B3-4AB0-A31C83D1E5E0> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/amtlib.framework/Versions/A/amtlib
 0x105b4e000 - 0x105c21ffb +AdobeJP2K (??? - ???) <BF2DBEA4-E71A-7112-53CA-8E7D73B1EFE5> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/AdobeJP2K.framework/Versions/A/AdobeJP2K
 0x105c41000 - 0x105c45ff8 +com.adobe.ape.shim (adbeape version 3.1.65.7508 - 3.1.65.7508) <0C380604-C686-C2E4-0535-C1FAB230187E> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/adbeape.framework/Versions/A/adbeape
 0x105c49000 - 0x105cc0fff +FileInfo (??? - ???) <6D5235B9-0EB6-17CA-6457-A2507A87EA8F> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/FileInfo.framework/Versions/A/FileInfo
 0x105ce1000 - 0x105d3fffd +AdobeXMP (??? - ???) <561026BB-C6EA-29CE-4790-CABCB81E8884> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/AdobeXMP.framework/Versions/A/AdobeXMP
 0x105d4d000 - 0x1061e8fff +com.nvidia.cg (2.2.0006 - ???) /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/Cg.framework/Cg
 0x10676e000 - 0x1067c4feb +com.adobe.headlights.LogSessionFramework (??? - 2.0.1.011) <03B80698-2C3B-A232-F15F-8F08F8963A19> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/LogSession.framework/Versions/A/LogSessio n
 0x106809000 - 0x10682effe +adobepdfsettings (??? - ???) <56E7F033-6032-2EC2-250E-43F1EBD123B1> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/adobepdfsettings.framework/Versions/A/ado bepdfsettings
 0x106868000 - 0x10686dffd +com.adobe.AdobeCrashReporter (3.0 - 3.0.20100302) <DFFB9A08-8369-D65F-161F-7C61D562E307> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/AdobeCrashReporter.framework/Versions/A/A dobeCrashReporter
 0x106872000 - 0x106a0efff +com.adobe.PlugPlug (2.0.0.109 - 2.0.0.109) <83092855-E671-F64A-EE0D-1110CF669634> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/PlugPlug.framework/Versions/A/PlugPlug
 0x106ab6000 - 0x106b99fff libcrypto.0.9.7.dylib (0.9.7 - compatibility 0.9.7) <358B5B40-43B2-3F92-9FD3-DAA68806E1FF> /usr/lib/libcrypto.0.9.7.dylib
 0x106bef000 - 0x106c08feb +libtbb.dylib (??? - ???) /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/libtbb.dylib
 0x106c19000 - 0x106c1ffeb +libtbbmalloc.dylib (??? - ???) /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/libtbbmalloc.dylib
 0x106c26000 - 0x106c26fff libmx.A.dylib (2026.0.0 - compatibility 1.0.0) <C23BF0A1-7E6D-35EF-85FE-651EE2C13D53> /usr/lib/libmx.A.dylib
 0x106c29000 - 0x106c31ff3 +com.adobe.boost_threads.framework (boost_threads version 5.0.0 - 5.0.0.0) <6858DF5A-F020-22A7-B945-14EC277724D4> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/boost_threads.framework/Versions/A/boost_ threads
 0x106fe0000 - 0x106fe2fff com.apple.textencoding.unicode (2.4 - 2.4) <FD4695F4-6110-36C6-AC06-86453E30FF6E> /System/Library/TextEncodings/Unicode Encodings.bundle/Contents/MacOS/Unicode Encodings
 0x1084e7000 - 0x1084f6ff7 libSimplifiedChineseConverter.dylib (54.0.0 - compatibility 1.0.0) <D5083346-BF48-325F-9399-06F4F9D7986C> /System/Library/CoreServices/Encodings/libSimplifiedChineseConverter. dylib
 0x1084fa000 - 0x1084fbff7 libCyrillicConverter.dylib (54.0.0 - compatibility 1.0.0) <B33779D3-937C-39A1-91E9-385B5268EF70> /System/Library/CoreServices/Encodings/libCyrillicConverter.dylib
 0x108700000 - 0x108770ff6 +com.adobe.amt.services (AMTServices 3.0.0.64 [BuildVersion: 3.0; BuildDate: Mon Jan 26 2010 21:49:00] - 3.0.0.64) <52FF1F9B-9991-ECE2-C7E3-09DA1B368CBE> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/amtservices.framework/Versions/a/amtservi ces
 0x1087d2000 - 0x1087edfff libJapaneseConverter.dylib (54.0.0 - compatibility 1.0.0) <489CAB2F-2854-3435-81CD-A062384016F7> /System/Library/CoreServices/Encodings/libJapaneseConverter.dylib
 0x109f89000 - 0x109faafff libKoreanConverter.dylib (54.0.0 - compatibility 1.0.0) <32EBCCBC-E862-3888-8202-B01053FDFECA> /System/Library/CoreServices/Encodings/libKoreanConverter.dylib
 0x109fae000 - 0x109fc0ff7 libTraditionalChineseConverter.dylib (54.0.0 - compatibility 1.0.0) <8F0BC42F-025B-3803-9C3E-FBD99199DFAA> /System/Library/CoreServices/Encodings/libTraditionalChineseConverter .dylib
 0x109fe4000 - 0x109fecfff +com.adobe.asneu.framework (asneu version 1.7.0.1 - 1.7.0.1) <3D59CB21-F5C7-4232-AB00-DFEB04206024> /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/Frameworks/asneu.framework/Versions/a/asneu
 0x10b627000 - 0x10b62efff +Enable Async IO (??? - ???) <3935C129-0FAE-3EAC-0CF2-4D740CD22E43> /Applications/Adobe Photoshop CS5/*/Enable Async IO.plugin/Contents/MacOS/Enable Async IO
 0x10b7d8000 - 0x10b7e1fff +FastCore (??? - ???) <25D92063-457F-C14A-6BE8-1C96C54F904C> /Applications/Adobe Photoshop CS5/*/FastCore.plugin/Contents/MacOS/FastCore
 0x10d600000 - 0x10d663ff3 +MMXCore (??? - ???) <2DB6FA8E-4373-9823-C4F5-A9F5F8F80717> /Applications/Adobe Photoshop CS5/*/MMXCore.plugin/Contents/MacOS/MMXCore
 0x10d6eb000 - 0x10d756ff0 +MultiProcessor Support (??? - ???) <4CDEDB26-96A2-631F-3C4B-FC3DBE9E2A02> /Applications/Adobe Photoshop CS5/*/MultiProcessor Support.plugin/Contents/MacOS/MultiProcessor Support
 0x1152e7000 - 0x1152ebfff com.apple.audio.AudioIPCPlugIn (1.2.0 - 1.2.0) <1EAF877E-4F15-39F7-89FA-D362AA4DA9DE> /System/Library/Extensions/AudioIPCDriver.kext/Contents/Resources/Aud ioIPCPlugIn.bundle/Contents/MacOS/AudioIPCPlugIn
 0x1152f0000 - 0x1152f6fff com.apple.audio.AppleHDAHALPlugIn (2.1.1 - 2.1.1f11) <A48CFDAF-9D81-3A14-8F67-9BAE253F73AE> /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHAL PlugIn.bundle/Contents/MacOS/AppleHDAHALPlugIn
 0x11569e000 - 0x1156c8fff com.apple.cmio.DAL.VDC_4 (201.0 - 3148) <3AFBD773-7BFE-385F-8D24-411A5686B41E> /System/Library/Frameworks/CoreMediaIO.framework/Resources/VDC.plugin /Contents/MacOS/VDC
 0x12186c000 - 0x121888ff7 +MeasurementCore (??? - ???) <23B22EB7-5FF8-BAAC-CA6D-084FDEA9AA5A> /Applications/Adobe Photoshop CS5/*/MeasurementCore.plugin/Contents/MacOS/MeasurementCore
 0x122372000 - 0x122392ffb +com.adobe.ape (adbeapecore version 3.1.70.10055 - 3.1.70.10055) <66373ADB-0865-ECDB-D3D0-B3373FC43919> /Library/Application Support/Adobe/*/adbeapecore.framework/adbeapecore
 0x1223bf000 - 0x1223edff7 GLRendererFloat (??? - ???) <AB59F7EA-62B1-3AA6-B940-47C0B6BC6DD9> /System/Library/Frameworks/OpenGL.framework/Resources/GLRendererFloat .bundle/GLRendererFloat
 0x122500000 - 0x12275dfef +com.adobe.PSAutomate (12.0.2 - 12.0.2) <2A43E60A-F63A-68A0-A73C-5BEEE05E6F33> /Applications/Adobe Photoshop CS5/*/ScriptingSupport.plugin/Contents/MacOS/ScriptingSupport
 0x12297c000 - 0x122a20ffb +com.adobe.AdobeExtendScript (ExtendScript 4.1.26 - 4.1.26.11099) <00717496-ACE1-7D2F-DEE7-4316D0AB52

Unfortunately this is not the case for me. Also using a late 2009 MBP and am having issues with PS CS5 and opening files. Doesn't matter what file size, large multiple layer psds or simple png screen shots. Randomly PS will freeze, black out the lower two thirds of the screen with the top portion of the screen flickering in what seems to be a lack of vertical sync. I was running PS with OpenGL in Basic mode on the 9400M when the issue first arose. I then switched to the 9600M to rule out video hardware problems and the issue persisted. I have also tested with both the 9400M and 9600M with OpenGL completely disabled and the issue still persists. Note that I always repair permissions before and after an upgrade only using the Combo Updates, I never use a delta through Software Update. Prior to updating to 10.6.4 I was running 10.6.3 without issue.
I guess there's nothing left to do at this point but downgrade to 10.6 and then back up to 10.6.3 - fun.

LAbview crashing after long test

Similar Messages

Maybe you are looking for