Monitor color problems...
good day all...
i just purchased a gateway 22 inch (fpd2275w)...hooked up via DVI...also had it via VGA...both ways gave off a bluish tinge..tried calibrating a million times...same tinge...is it my video card? i also have the 17 studio display lcd...via ADC...Which looks great...side by side definite difference...any help would be great...also when in itunes (7.1.1) it has the new feature of expanding cover flow to full screen...the gateway has these diagonal black lines thru the album covers which does not show up on the apple display....
thanx again
Refer to your Gateway manual. Usually there are settings for color adjust that are independent of the computer or other driving source. You can probably get a warmer color setting in this way.
Similar Messages
-
Pavilion gv laptop colors on monitor color problem
I'm having color problems on my laptop. While the colors on my screen aren't terrible,most of the color/textures appear washed out and muted in comparison to other laptops I own. I've tried adjusting the brightness and calibrating the colors but it didn't fix the problem. I'm not sure what the problem could be. Thank you for your help.
Hey @crawford810 ,
Welcome to the HP Forums!
I understand the colours on your notebook look muted.
Could you please tell me which notebook model you have and the installed operating system? For information on finding your product and model numbers click here: How Do I Find My Model Number or Product Number? To see which version of Windows you are using click here: Which Windows operating system am I running?
For an issue like this you will want to test an external monitor to see if the issue is coming from the display, the GPU, or from Windows.
You will want to make sure your GPU and BIOS are up to date. You can download the most recent drivers and BIOS at the HP - Drivers & Downloads website.
I look forward to your reply!
Please click the "Kudos, Thumbs Up" at the bottom of this post if you want to say "Thanks" for helping!
Please click "Accept as Solution" if you feel my post solved your issue, it will help others find the solution.
The Great Deku Tree
I work on behalf of HP. -
Photoshop CS5 Mac Dual Monitor color problems
Hi all,
I know this problem has been raised before, but I can't seem to find a definitive answer - there is a lot of conjecture and opposing opinions so I'm trying to get to the bottom of this once and for all.
Gear: MacBook Pro, Photoshop CS5, Wacom Cintiq 12WX as second display, Mac OS X 10.7.4
Problem: Photoshop seems to only use the Monitor Profile of the main display (i.e. the one with the menu bar in System Preferences>Displays>Arrangement) - some people say yes, this is the case, some people say no, Photoshop uses independent profiles for each display.
Manifestation: If I set my MacBook screen to the main display, color looks good in Photoshop on the MacBook and terrible on the Wacom and vice-versa. However, in Lightroom and other applications changing the main display makes no difference to the output on each display.
Preferred solution: I would like to have my MacBook as my main display with menu bars and dock etc, but then I want the Cintiq to be the display I use in Photoshop, for obvious reasons. In my workflow, I would like to have my image open in 2 windows, one on the Cintiq for retouching and one on the MacBook to check progress and color etc
Curveball: I have a trial of CS6 and the problem seems to be fixed (maybe, my eyes and sense of reason are fried)
Many thanks for any help anyone can shed
SimonMake sure you have all the updates installed for Photoshop.
Apple introduced new bugs in their display and window update pipelines in 10.7, which we didn't get a chance to completely work around until Photoshop CS6.
We tried to work around them as best we could in the dot releases for CS5. -
Apple color monitor color problem
look at a picture of my monitor, what can do?
Looks like a graphics card issue. Either it doesn't have enough RAM, or is unsupported.
Besides, that monitor interface inside Color is completely inaccurate. It's only for reference. Color is designed to work with an IO device and send a signal out to a broadcast monitor or HDTV. If you graded by judging what you saw on that monitor (if it was working) you'd be way off...it'd look very different when you exported a master file.
The IO devices that work with iMacs are AJA and Decklink Thunderbolt models...only if your iMac has Thunderbolt. The only firewire devices are no longer made (and they were crazy expensive) -
The monitor colors were abnormal
My Mac air has an external monitor, Dell u2414h, connected through DP cable ( Mini-DP to DP). In these days, I encountered a monitor color issue, might be a bug or a hardware problem, maybe someone have this experience to confirm that, thanks in advance.
the process:
1. The Mac air connected to the external monitor, Both of the internal an external monitors are used normally;
2. closed the Mac air lid, the external monitor was still opening at this time and the OS X system can be operated normally;
3. I left the notebook to do other things;
4. About five minutes later the external monitor went to sleep;
5. More than one hour later, I came back, the OS X system was sleep, opened the lid;
6. Both of the internal and external monitors' colors were abnormal, some application icons and the desktop wallpaper had red blocks; These red blocks on the desktop wallpaper didn't disappear automatcally, must to replace a new wallpaper;
The system.log has "GPU hang:" and "Trying restart GPU ..." messages;
The loginwindow crashed, and saved a crash report;
This issue occured several times;
the system.log
May 14 10:20:56 mar kernel[0]: TBT W (2): 0x0100 [x]
May 14 10:20:56 mar kernel[0]: Wake reason: EC.LidOpen (User)
May 14 10:20:56 mar kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000320
May 14 10:20:56 mar kernel[0]: 66066.440417: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
May 14 10:20:56 mar kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340
May 14 10:20:56 mar kernel[0]: RTC: PowerByCalendarDate setting ignored
May 14 10:20:56 mar kernel[0]: Previous Sleep Cause: 5
May 14 10:20:56 mar kernel[0]: AppleHSSPIController::HandleMessage Device Wake by Host
May 14 10:20:56 mar.local hidd[60]: MultitouchHID: device bootloaded
May 14 10:20:56 mar.local SystemUIServer[269]: HALDefaultDevice::GetDefaultDevice: got an error getting the default device from the server, so picking one locally
May 14 10:20:56 mar.local NotificationCenter[280]: HALDefaultDevice::GetDefaultDevice: got an error getting the default device from the server, so picking one locally
May 14 10:20:56 mar kernel[0]: Sound assertion in AppleHDAController at line 5050
May 14 10:20:56 mar kernel[0]: wlEvent: en0 en0 Link DOWN virtIf = 0
May 14 10:20:56 mar kernel[0]: AirPort: Link Down on en0. Reason 8 (Disassociated because station leaving).
May 14 10:20:56 mar kernel[0]: en0::IO80211Interface::postMessage bssid changed
May 14 10:20:57 mar.local configd[17]: network changed: v4(en0-:10.12.1.10) DNS- Proxy- SMB
May 14 10:20:59 mar kernel[0]: Sound assertion - Command/Response TIMED OUT and ( kRequestStateMatch == fCodecRequest->state = 2 ), fCodecRequest->command->codec: 0xffffff802b663b00, fCodecRequest->command->verb: 0x1F0500, fPoweredDown: 1
May 14 10:20:59 mar kernel[0]: Sound assertion in AppleHDAController at line 5466
May 14 10:20:59 mar kernel[0]: Sound assertion in AppleHDAController at line 5468
May 14 10:20:59 mar kernel[0]: Sound assertion in IOHDACodecDevice at line 161
May 14 10:20:59 mar kernel[0]: Sound assertion in AppleHDANode at line 308
May 14 10:20:59 mar kernel[0]: Sound assertion in AppleHDAPathSet at line 272
May 14 10:20:59 mar kernel[0]: 66070.114904: MacAuthEvent en0 Auth result for: 00:1a:28:22:e5:88 MAC AUTH succeeded
May 14 10:20:59 mar kernel[0]: wlEvent: en0 en0 Link UP virtIf = 0
May 14 10:20:59 mar kernel[0]: AirPort: Link Up on en0
May 14 10:20:59 mar kernel[0]: en0: BSSID changed to 00:1a:28:22:e5:88
May 14 10:20:59 mar kernel[0]: en0::IO80211Interface::postMessage bssid changed
May 14 10:20:59 mar kernel[0]: AirPort: RSN handshake complete on en0
May 14 10:21:00 mar.local airportd[778]: _doAutoJoin: Already associated to “tp-link”. Bailing on auto-join.
May 14 10:21:02 --- last message repeated 1 time ---
May 14 10:21:02 mar kernel[0]: GPU hang:
May 14 10:21:02 mar kernel[0]: Trying restart GPU ...
May 14 10:21:02 mar kernel[0]: MAIN ring is stuck waiting on an event
May 14 10:21:02 mar kernel[0]: After attempt to clear wait condition = 0x0000f001 no longer waiting
May 14 10:21:02 mar.local configd[17]: network changed: v4(en0+:10.12.1.10) DNS+ Proxy+ SMB
May 14 10:21:02 mar.local UserEventAgent[11]: Captive: en0: Not probing 'tp-link' (protected network)
May 14 10:21:02 mar.local configd[17]: network changed: v4(en0!:10.12.1.10) DNS Proxy SMB
May 14 10:21:06 mar.local airportd[778]: _doAutoJoin: Already associated to “tp-link”. Bailing on auto-join.
May 14 10:21:06 mar kernel[0]: GPU hang:
May 14 10:21:06 mar kernel[0]: Trying restart GPU ...
May 14 10:21:06 mar kernel[0]: MAIN ring is NOT waiting on an event
May 14 10:21:06 mar kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340
May 14 10:21:06 mar kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000300
May 14 10:21:06 mar kernel[0]: AppleCamIn::wakeEventHandlerThread
May 14 10:21:06 mar kernel[0]: en0: BSSID changed to 00:1a:28:22:e5:88
May 14 10:21:07 mar.local ReportCrash[2144]: DebugSymbols was unable to start a spotlight query: spotlight is not responding or disabled.
May 14 10:21:07 mar.local WindowServer[101]: Created shield window 0xcef for display 0x003f003c
May 14 10:21:07 mar.local WindowServer[101]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7f91c3e62b00(2004), shield 0x7f91c5133e00(2001), lock state 3
May 14 10:21:07 mar.local WindowServer[101]: handle_will_sleep_auth_and_shield_windows: err 0x0
May 14 10:21:08 mar.local ReportCrash[2144]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
May 14 10:21:08 mar.local ReportCrash[2144]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
May 14 10:21:08 mar.local ReportCrash[2144]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
May 14 10:21:08 mar.local ReportCrash[2144]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
May 14 10:21:08 mar.local ReportCrash[2144]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
May 14 10:21:08 mar.local ReportCrash[2144]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
May 14 10:21:08 mar.local ReportCrash[2144]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
May 14 10:21:08 mar.local ReportCrash[2144]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
May 14 10:21:08 mar.local ReportCrash[2144]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
May 14 10:21:08 mar.local ReportCrash[2144]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
May 14 10:21:08 mar com.apple.launchd[1] (com.apple.loginwindow[56]): Job appears to have crashed: Abort trap: 6
May 14 10:21:08 mar.local coreservicesd[31]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyBringForwardRequest to notificationID=101
May 14 10:21:08 mar.local coreservicesd[31]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=123
May 14 10:21:08 mar.local coreservicesd[31]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=127
May 14 10:21:08 mar.local coreservicesd[31]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=100
May 14 10:21:08 mar.local coreservicesd[31]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=138
May 14 10:21:08 mar.local Dock[267]: Lost connection with usernoted.
May 14 10:21:08 mar.local UserEventAgent[11]: Captive: [UserAgentDied:139] User Agent @port=16139 Died
May 14 10:21:08 mar com.apple.launchd.peruser.501[231] ([0x0-0x11011].com.apple.iTunesHelper[298]): Exited with code: 1
May 14 10:21:08 mar com.apple.launchd.peruser.501[231] (com.apple.Dock.agent[267]): Exited with code: 1
May 14 10:21:08 mar.local coreservicesd[31]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=174
May 14 10:21:08 mar.local coreservicesd[31]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyChildDeath to notificationID=164
May 14 10:21:08 mar.local PhotoStreamAgent[275]: Check-in to the service com.apple.usernoted.client failed. This is likely because you have either unloaded the job or the MachService has the ResetAtClose attribute specified in the launchd.plist. If present, this attribute should be removed.
May 14 10:21:08 mar.local imagent[284]: Quit - notifying about shutdown
May 14 10:21:08 mar.local imagent[284]: Quit - shutting down daemon
May 14 10:21:08 mar.local login[881]: DEAD_PROCESS: 881 ttys001
May 14 10:21:08 mar.local login[337]: DEAD_PROCESS: 337 ttys000
May 14 10:21:08 mar.local loginwindow[2146]: Login Window Application Started
May 14 10:21:09 mar.local ReportCrash[2144]: Saved crash report for loginwindow[56] version 8.3 (8.3) to /Library/Logs/DiagnosticReports/loginwindow_2014-05-14-289012_mar.crash
May 14 10:21:12 mar kernel[0]: AppleCamIn::handleWakeEvent_gated
May 14 10:21:12 mar kernel[0]: AppleCamIn::acpiControlS2ChipPower - powerState=0, status = 0x0, result_value = 0x0
May 14 10:21:12 mar kernel[0]: GPU hang:
May 14 10:21:12 mar kernel[0]: Trying restart GPU ...
May 14 10:21:12 mar kernel[0]: MAIN ring is NOT waiting on an event
May 14 10:21:13 mar kernel[0]: EDID CEA Extensions not valid for audio. [Checksum]
May 14 10:21:13 mar.local WindowServer[101]: Received display connect changed for display 0x3f003c
May 14 10:21:13 mar.local WindowServer[101]: Created shield window 0xcf0 for display 0x04273c80
May 14 10:21:13 mar.local WindowServer[101]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7f91c3e62b00(2002), shield 0x7f91c5133e00(2001), lock state 3
May 14 10:21:13 mar.local WindowServer[101]: handle_will_sleep_auth_and_shield_windows: err 0x0
May 14 10:21:13 mar.local WindowServer[101]: Received display connect changed for display 0x2b287dcd
May 14 10:21:13 mar.local WindowServer[101]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7f91c3e62b00(2002), shield 0x7f91c5133e00(2001), lock state 3
May 14 10:21:13 mar.local WindowServer[101]: handle_will_sleep_auth_and_shield_windows: err 0x0
May 14 10:21:13 mar.local WindowServer[101]: Received display connect changed for display 0x3f003e
May 14 10:21:13 mar.local WindowServer[101]: dict count after removing entry for window 0x37 is 0
May 14 10:21:13 mar.local WindowServer[101]: CGXRestartSessionWorkspace: session workspace exited for session 256 (on console)
May 14 10:21:13 mar.local WindowServer[101]: Session 256 released (1 references)
May 14 10:21:13 mar.local WindowServer[101]: Session 256 released (0 references)
May 14 10:21:13 mar.local WindowServer[101]: loginwindow connection closed; closing server.
May 14 10:21:13 mar.local firefox[2046]: CGSGetNextEventRecord (Inline) connection 0xb6f3, 16384 bytes
May 14 10:21:13 mar.local firefox[2046]: CGSShutdownServerConnections: Detaching application from window server
May 14 10:21:13 mar.local firefox[2046]: CGSDisplayServerShutdown: Detaching display subsystem from window server
May 14 10:21:13 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:13 mar.local firefox[2046]: HIToolbox: received notification of WindowServer event port death.
May 14 10:21:13 mar.local firefox[2046]: port matched the WindowServer port created in BindCGSToRunLoop
May 14 10:21:13 mar.local firefox[2046]: kCGErrorRangeCheck: On-demand launch of the Window Server is allowed for root user only.
May 14 10:21:13 mar.local firefox[2046]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1102)
May 14 10:21:13 mar.local firefox[2046]: kCGErrorRangeCheck: On-demand launch of the Window Server is allowed for root user only.
May 14 10:21:13 mar.local firefox[2046]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1102)
May 14 10:21:13 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:13 --- last message repeated 18 times ---
May 14 10:21:13 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:13 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:13 mar.local WindowServer[2148]: Server is starting up
May 14 10:21:13 mar.local WindowServer[2148]: Session 256 retained (2 references)
May 14 10:21:13 mar.local WindowServer[2148]: Session 256 released (1 references)
May 14 10:21:13 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:13 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:13 mar.local WindowServer[2148]: Session 256 retained (2 references)
May 14 10:21:13 mar.local WindowServer[2148]: init_page_flip: page flip mode is on
May 14 10:21:13 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:13 --- last message repeated 1 time ---
May 14 10:21:13 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:13 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:13 mar.local WindowServer[2148]: mux_initialize: Couldn't find any matches
May 14 10:21:13 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:13 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:13 mar.local WindowServer[2148]: GLCompositor enabled for tile size [256 x 256]
May 14 10:21:13 mar.local WindowServer[2148]: CGXGLInitMipMap: mip map mode is on
May 14 10:21:13 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:13 --- last message repeated 1 time ---
May 14 10:21:13 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:13 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:13 mar.local WindowServer[2148]: WSMachineUsesNewStyleMirroring: true
May 14 10:21:13 mar.local WindowServer[2148]: MPServiceForDisplayDevice: Invalid device alias (0)
May 14 10:21:13 mar.local WindowServer[2148]: Display 0x5b81908d: GL mask 0x2; bounds (0, 0)[1920 x 1080], 16 modes available
Main, Active, on-line, enabled, Vendor 756e6b6e, Model 717, S/N 5618130e, Unit 1, Rotation 0
UUID 0x756e6b6e000007175618130e00000000
May 14 10:21:13 mar.local WindowServer[2148]: Display 0x003f003e: GL mask 0x4; bounds (0, 0)[0 x 0], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 2, Rotation 0
UUID 0xffffffffffffffffffffffff1272e91b
May 14 10:21:13 mar.local WindowServer[2148]: Display 0x04273c80: GL mask 0x1; bounds (-1366, 0)[1366 x 768], 10 modes available
Active, on-line, enabled, built-in, boot, Vendor 610, Model 9cf2, S/N 0, Unit 0, Rotation 0
UUID 0x0000061000009cf2000000000b828667
May 14 10:21:13 mar.local WindowServer[2148]: Created shield window 0x5 for display 0x5b81908d
May 14 10:21:13 mar.local WindowServer[2148]: Created shield window 0x6 for display 0x003f003e
May 14 10:21:13 mar.local WindowServer[2148]: Created shield window 0x7 for display 0x04273c80
May 14 10:21:13 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:13 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:13 mar.local WindowServer[2148]: Display 0x5b81908d: GL mask 0x2; bounds (0, 0)[1920 x 1080], 16 modes available
Main, Active, on-line, enabled, Vendor 756e6b6e, Model 717, S/N 5618130e, Unit 1, Rotation 0
UUID 0x756e6b6e000007175618130e00000000
May 14 10:21:13 mar.local WindowServer[2148]: Display 0x003f003e: GL mask 0x4; bounds (2944, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 2, Rotation 0
UUID 0xffffffffffffffffffffffff1272e91b
May 14 10:21:13 mar.local WindowServer[2148]: Display 0x04273c80: GL mask 0x1; bounds (-1366, 0)[1366 x 768], 10 modes available
Active, on-line, enabled, built-in, boot, Vendor 610, Model 9cf2, S/N 0, Unit 0, Rotation 0
UUID 0x0000061000009cf2000000000b828667
May 14 10:21:13 mar.local WindowServer[2148]: CGXPerformInitialDisplayConfiguration
May 14 10:21:13 mar.local WindowServer[2148]: Display 0x5b81908d: MappedDisplay Unit 1; Vendor 0x756e6b6e Model 0x717 S/N 372032402 Dimensions 0.00 x 0.00; online enabled, Bounds (0,0)[1920 x 1080], Rotation 0, Resolution 1
May 14 10:21:13 mar.local WindowServer[2148]: Display 0x003f003e: MappedDisplay Unit 2; Vendor 0xffffffff Model 0xffffffff S/N -1 Dimensions 0.00 x 0.00; offline enabled, Bounds (2944,0)[1 x 1], Rotation 0, Resolution 1
May 14 10:21:13 mar.local WindowServer[2148]: Display 0x04273c80: MappedDisplay Unit 0; Vendor 0x610 Model 0x9cf2 S/N 0 Dimensions 10.08 x 5.67; online enabled built-in, Bounds (-1366,0)[1366 x 768], Rotation 0, Resolution 1
May 14 10:21:13 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:13 mar.local WindowServer[2148]: GLCompositor: GL renderer id 0x01024500, GL mask 0x00000007, accelerator 0x00004093, unit 0, caps QEX|QGL|MIPMAP, vram 1024 MB
May 14 10:21:13 mar.local WindowServer[2148]: GLCompositor: GL renderer id 0x01024500, GL mask 0x00000007, texture units 8, texture max 16384, viewport max {16384, 16384}, extensions FPRG|NPOT|GLSL|FLOAT
May 14 10:21:13 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:13 mar.local loginwindow[2146]: **DMPROXY** Found `/System/Library/CoreServices/DMProxy'.
May 14 10:21:13 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:13 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:13 --- last message repeated 1 time ---
May 14 10:21:13 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:13 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:13 --- last message repeated 2 times ---
May 14 10:21:13 mar.local WindowServer[2148]: Created shield window 0x8 for display 0x5b81908d
May 14 10:21:13 mar.local WindowServer[2148]: Display 0x5b81908d: MappedDisplay Unit 1; ColorProfile { 2, "Display"}; TransferFormula (1.229050, 1.229050, 1.229050)
May 14 10:21:13 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:13 mar.local WindowServer[2148]: Created shield window 0x9 for display 0x04273c80
May 14 10:21:13 mar.local WindowServer[2148]: Display 0x04273c80: MappedDisplay Unit 0; ColorProfile { 3, "Color LCD"}; TransferTable (256, 3)
May 14 10:21:13 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:13 --- last message repeated 1 time ---
May 14 10:21:13 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:13 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:13 --- last message repeated 1 time ---
May 14 10:21:13 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:13 mar.local airportd[778]: _doAutoJoin: Already associated to “tp-link”. Bailing on auto-join.
May 14 10:21:13 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:13 mar.local launchctl[2150]: com.apple.findmymacmessenger: Already loaded
May 14 10:21:13 mar.local launchctl[2150]: com.apple.store_helper: Already loaded
May 14 10:21:13 mar.local launchctl[2150]: com.apple.storeagent: Already loaded
May 14 10:21:13 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:13 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:13 mar.local hidd[60]: CGSShutdownServerConnections: Detaching application from window server
May 14 10:21:13 mar.local hidd[60]: CGSDisplayServerShutdown: Detaching display subsystem from window server
May 14 10:21:13 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:13 --- last message repeated 2 times ---
May 14 10:21:13 mar.local com.apple.SecurityServer[15]: Session 100091 created
May 14 10:21:13 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:13 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:13 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:13 mar.local loginwindow[2146]: Login Window Started Security Agent
May 14 10:21:13 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 2 times ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 mar.local SecurityAgent[2157]: MacBuddy was run = 0
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local WindowServer[2148]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x5b81908d device: 0x1010b1110 isBackBuffered: 1 numComp: 3 numDisp: 3
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 mar.local CVMServer[197]: Check-in to the service com.apple.cvmsCompAgent_x86_64 failed. This is likely because you have either unloaded the job or the MachService has the ResetAtClose attribute specified in the launchd.plist. If present, this attribute should be removed.
May 14 10:21:14 mar.local WindowServer[2148]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x04273c80 device: 0x1010b1d10 isBackBuffered: 1 numComp: 3 numDisp: 3
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local CVMServer[197]: Check-in to the service com.apple.cvmsCompAgent_x86_64 failed. This is likely because you have either unloaded the job or the MachService has the ResetAtClose attribute specified in the launchd.plist. If present, this attribute should be removed.
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 mar.local locationd[2159]: Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatiblity mapping behavior in the near future.
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local locationd[2159]: NOTICE,Location icon should now be in state 0
May 14 10:21:14 mar.local UserEventAgent[2152]: cannot find useragent 1102
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local CVMServer[197]: Check-in to the service com.apple.cvmsCompAgent_x86_64 failed. This is likely because you have either unloaded the job or the MachService has the ResetAtClose attribute specified in the launchd.plist. If present, this attribute should be removed.
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 mar.local CVMServer[197]: Check-in to the service com.apple.cvmsCompAgent_x86_64 failed. This is likely because you have either unloaded the job or the MachService has the ResetAtClose attribute specified in the launchd.plist. If present, this attribute should be removed.
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 mar.local SecurityAgent[2157]: *** WARNING: -[NSImage compositeToPoint:operation:fraction:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
May 14 10:21:14 mar.local SecurityAgent[2157]: *** WARNING: -[NSImage compositeToPoint:fromRect:operation:fraction:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 2 times ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local SecurityAgent[2157]: *** WARNING: -[NSImage compositeToPoint:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
May 14 10:21:14 mar.local SecurityAgent[2157]: *** WARNING: -[NSImage compositeToPoint:fromRect:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 1 time ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:14 --- last message repeated 3 times ---
May 14 10:21:14 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:14 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:15 --- last message repeated 1 time ---
May 14 10:21:15 mar.local firefox[2046]: CGSFlushWindowContentRegion: Invalid connection
May 14 10:21:15 mar.local firefox[2046]: CGSGetDisplayBounds: Invalid display 0x00000000
May 14 10:21:15 --- last message repeated 2 times ---
the loginwindow crash report:
Process: loginwindow [56]
Path: /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow
Identifier: loginwindow
Version: 8.3 (8.3)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2014-05-14 10:23:06.970 +0800
OS Version: Mac OS X 10.8.5 (12F45)
Report Version: 10
Sleep/Wake UUID: 307EEC64-FD66-9C42-BCF6-D66214EDAC0F
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
abort() called
Application Specific Signatures:
Graphics hardware encountered an error and was reset: 0x00000000
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff8b686212 __pthread_kill + 10
1 libsystem_c.dylib 0x00007fff86693b24 pthread_kill + 90
2 libsystem_c.dylib 0x00007fff866d7f61 abort + 143
3 libGPUSupportMercury.dylib 0x000000010fbeb456 gpusKillClient + 87
4 libGPUSupportMercury.dylib 0x000000010fbec7f5 gpusSubmitDataBuffers + 179
5 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x00000001142b8d0e IntelCommandBuffer::getNew(GLDContextRec*) + 54
6 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x00000001142b522f GenContext::prepareCommandBuffer() + 23
7 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x00000001142b8a64 intelSubmitCommands + 198
8 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x00000001142b9c2f SwapFlush(GLDContextRec*, unsigned int) + 22
9 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x00000001142b9f45 gldPresentFramebufferData + 144
10 GLEngine 0x0000000113c0181e glSwap_Exec + 110
11 com.apple.opengl 0x00007fff8ae73717 CGLFlushDrawable + 69
12 com.apple.QuartzCore 0x00007fff8b35fede view_draw(_CAView*, double, CVTimeStamp const*, bool) + 4612
13 com.apple.QuartzCore 0x00007fff8b35ec69 CAViewDraw + 174
14 com.apple.AppKit 0x00007fff8cbd8fa2 -[NSView(NSLayerKitGlue) _drawRectAsLayerTree:] + 571
15 com.apple.AppKit 0x00007fff8ca8827a -[NSView _drawRect:clip:] + 4751
16 com.apple.AppKit 0x00007fff8ca84fb3 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 3058
17 com.apple.AppKit 0x00007fff8ca85a44 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 5763
18 com.apple.AppKit 0x00007fff8cbd3fab -[NSNextStepFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 286
19 com.apple.AppKit 0x00007fff8ca7fd6d -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 4675
20 com.apple.AppKit 0x00007fff8ca49c93 -[NSView displayIfNeeded] + 1830
21 com.apple.AppKit 0x00007fff8cbd3e64 -[NSNextStepFrame displayIfNeeded] + 84
22 com.apple.AppKit 0x00007fff8ca491cc _handleWindowNeedsDisplayOrLayoutOrUpdateConstraints + 738
23 com.apple.AppKit 0x00007fff8d014901 __83-[NSWindow _postWindowNeedsDisplayOrLayoutOrUpdateConstraintsUnlessPostingDisabled]_block_ invoke_01208 + 46
24 com.apple.CoreFoundation 0x00007fff9095c417 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
25 com.apple.CoreFoundation 0x00007fff9095c381 __CFRunLoopDoObservers + 369
26 com.apple.CoreFoundation 0x00007fff909377b8 __CFRunLoopRun + 728
27 com.apple.CoreFoundation 0x00007fff909370e2 CFRunLoopRunSpecific + 290
28 com.apple.HIToolbox 0x00007fff91007eb4 RunCurrentEventLoopInMode + 209
29 com.apple.HIToolbox 0x00007fff91007c52 ReceiveNextEventCommon + 356
30 com.apple.HIToolbox 0x00007fff91007ae3 BlockUntilNextEventMatchingListInMode + 62
31 com.apple.AppKit 0x00007fff8ca46533 _DPSNextEvent + 685
32 com.apple.AppKit 0x00007fff8ca45df2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
33 com.apple.AppKit 0x00007fff8ca3d1a3 -[NSApplication run] + 517
34 com.apple.loginwindow 0x000000010f8cbba8 0x10f8c6000 + 23464
35 libdyld.dylib 0x00007fff86b7c7e1 start + 1
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff8b686d16 kevent + 10
1 libdispatch.dylib 0x00007fff90c23dea _dispatch_mgr_invoke + 883
2 libdispatch.dylib 0x00007fff90c239ee _dispatch_mgr_thread + 54
Thread 2:: CVDisplayLink
0 libsystem_kernel.dylib 0x00007fff8b686122 __psynch_mutexwait + 10
1 libsystem_c.dylib 0x00007fff86697dcd pthread_mutex_lock + 536
2 com.apple.QuartzCore 0x00007fff8b3689e9 view_display_link(double, CVTimeStamp const*, void*) + 33
3 com.apple.QuartzCore 0x00007fff8b36893e link_callback + 244
4 com.apple.CoreVideo 0x00007fff8bb2100b CVDisplayLink::performIO(CVTimeStamp*) + 203
5 com.apple.CoreVideo 0x00007fff8bb20271 CVDisplayLink::runIOThread() + 641
6 com.apple.CoreVideo 0x00007fff8bb1ffd7 startIOThread(void*) + 148
7 libsystem_c.dylib 0x00007fff86692772 _pthread_start + 327
8 libsystem_c.dylib 0x00007fff8667f1a1 thread_start + 13
Thread 3:
0 libsystem_kernel.dylib 0x00007fff8b6866d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff86694f1c _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff86694ce3 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff8667f191 start_wqthread + 13
Thread 4:: Dispatch queue: com.apple.root.default-priority
0 libsystem_c.dylib 0x00007fff866b98bc small_malloc_from_free_list + 275
1 libsystem_c.dylib 0x00007fff866b9436 szone_malloc_should_clear + 3321
2 libsystem_c.dylib 0x00007fff866ab183 malloc_zone_malloc + 71
3 libsystem_c.dylib 0x00007fff866abbd7 malloc + 41
4 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x000000011422489f USC::CMultiPoolAllocator<USC::CAllocator, USC::ISAScheduler::CMPAllocatorProfileISAScheduler>::CPoolAllocator::AllocateBl ock() + 21
5 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x0000000114224859 USC::CMultiPoolAllocator<USC::CAllocator, USC::ISAScheduler::CMPAllocatorProfileISAScheduler>::CPoolAllocator::Allocate(u nsigned long) + 59
6 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x000000011422b93f USC::ISAScheduler::CEdge::Create(USC::CMultiPoolAllocator<USC::CAllocator, USC::ISAScheduler::CMPAllocatorProfileISAScheduler>&, USC::ISAScheduler::CDagNode*, USC::ISAScheduler::CDagNode*, USC::ISAScheduler::EdgeType, unsigned int, USC::ISAScheduler::RegisterType, USC::ISAScheduler::CEdge*&) + 47
7 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x000000011422c2a6 USC::ISAScheduler::CDependenceDAG::AddEdge(USC::ISAScheduler::CDagNode*, USC::ISAScheduler::CDagNode*, USC::ISAScheduler::EdgeType, unsigned int, USC::ISAScheduler::RegisterType, unsigned int) + 242
8 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x000000011422c39e USC::ISAScheduler::CDependenceDAG::AddEdges(USC::ISAScheduler::CDagNode*, USC::ISAScheduler::CInstInfo*, USC::ISAScheduler::CRegIterator, USC::ISAScheduler::CISCDagOptLinkedList<USC::CMultiPoolAllocator<USC::CAllocato r, USC::ISAScheduler::CMPAllocatorProfileISAScheduler> >**, USC::ISAScheduler::EdgeType, USC::ISAScheduler::CDagNode**, USC::ISAScheduler::EdgeType) + 94
9 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x000000011422d673 USC::ISAScheduler::CDependenceDAG::AddNodeEdges(USC::ISAScheduler::CDagNode*, USC::ISAScheduler::CDagNode*) + 567
10 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x000000011422d140 USC::ISAScheduler::CDependenceDAG::Build() + 1074
11 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x0000000114223793 USC::ISAScheduler::CScheduler::Schedule(void const*) + 661
12 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x00000001142233dd USC::CGen4CodeGeneratorContext::LocalScheduling(USC::CShader const*, unsigned int*) + 189
13 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x00000001141948f5 USC::CGen6PixelShaderKernelProgram::Compile16(bool, bool) + 749
14 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x0000000114193aa8 USC::CGen6PixelShaderKernelProgram::Build() + 306
15 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x0000000114193931 USC::CGen6PixelShaderKernelProgram::Initialize() + 291
16 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x00000001141935ba USC::CGen6PixelShaderKernelProgram::Create(void const*, PLATFORM_STR, S3DKernelHardwareCapabilities const&, USC::CPixelShader*, USC::OPTIMIZER_LEVEL, USC::SIMD_LEVEL, USC::SGen6PixelShaderKernelProgramCacheKey const*, USC::CGen6PixelShaderKernelProgram*&) + 434
17 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x0000000114198484 USC::CPixelShader::Compile(USC::OPTIMIZER_LEVEL, USC::SIMD_LEVEL, USC::SPixelShaderCompileTimeOptions const&, USC::SPixelShaderDrawTimeData const&, USC::SCompilerOutputPixelShader_Gen7*&) + 758
18 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x00000001140abcdc USC::CompilePixelShaderOpenGL(void*, USC::OPTIMIZER_LEVEL, USC::SIMD_LEVEL, USC::SCompilerInputStatePixelShaderOpenGL const*, USC::SCompilerOutputPixelShaderOpenGL_Gen7*&) + 890
19 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x000000011434c9b9 __Compile_block_invoke_0 + 53
20 libdispatch.dylib 0x00007fff90c24f01 _dispatch_call_block_and_release + 15
21 libdispatch.dylib 0x00007fff90c210b6 _dispatch_client_callout + 8
22 libdispatch.dylib 0x00007fff90c221fa _dispatch_worker_thread2 + 304
23 libsystem_c.dylib 0x00007fff86694cdb _pthread_wqthread + 404
24 libsystem_c.dylib 0x00007fff8667f191 start_wqthread + 13
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff50335c78 rdx: 0x0000000000000000
rdi: 0x0000000000000707 rsi: 0x0000000000000006 rbp: 0x00007fff50335ca0 rsp: 0x00007fff50335c78
r8: 0x00007fff75d01278 r9: 0x0000000000000010 r10: 0x0000000020000000 r11: 0x0000000000000206
r12: 0x0000000000000002 r13: 0x00007ff8eb82dfe0 r14: 0x00007fff75d02180 r15: 0x00007ff8eb82a800
rip: 0x00007fff8b686212 rfl: 0x0000000000000206 cr2: 0x00007fff75cfaff0
Logical CPU: 0
Binary Images:
0x10f8c6000 - 0x10f958ff7 com.apple.loginwindow (8.3 - 8.3) <AB3B6690-DF7F-32E1-84CB-3102AC24E5E5> /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow
0x10fa1c000 - 0x10fa1dfff com.apple.heimdalodpac (10.8 - 198) <AE9D93D6-C970-368B-A89C-2DA0EB225204> /System/Library/KerberosPlugins/KerberosFrameworkPlugins/heimdalodpac.bundle/Co ntents/MacOS/heimdalodpac
0x10fa26000 - 0x10fa28fff com.apple.KerberosHelper.LKDCLocate (4.0 - 1.0) <6276FDFA-EB44-374C-9BFC-2AB5F68F2145> /System/Library/KerberosPlugins/KerberosFrameworkPlugins/LKDCLocate.bundle/Cont ents/MacOS/LKDCLocate
0x10fa2c000 - 0x10fa2dff7 com.apple.kerberos.reachability (3.0 - 2.0) <C1D06251-8E52-36F4-B309-D4DA4DEA02FF> /System/Library/KerberosPlugins/KerberosFrameworkPlugins/Reachability.bundle/Co ntents/MacOS/Reachability
0x10fa31000 - 0x10fa32ff7 com.apple.kerberos.sckerberosconfig (3.0 - 1) <D853071E-46AC-3475-B1FE-93BAD3C13617> /System/Library/KerberosPlugins/KerberosFrameworkPlugins/SCKerberosConfig.bundl e/Contents/MacOS/SCKerberosConfig
0x10fa89000 - 0x10fa89fff pam_self.so.2 (135.1) <4303A0B2-BDA1-3105-93D9-40570F115550> /usr/lib/pam/pam_self.so.2
0x10fa8f000 - 0x10fa8ffff pam_deny.so.2 (20) <FB097173-E842-3909-8F3E-67CCA412489C> /usr/lib/pam/pam_deny.so.2
0x10fb26000 - 0x10fb26fff pam_group.so.2 (135.1) <E2644A5A-33D1-3377-A180-4D1CA9F808F3> /usr/lib/pam/pam_group.so.2
0x10fb2c000 - 0x10fb31fff pam_krb5.so.2 (135.1) <DDB17329-C4EE-3467-9B0E-76F29C1D1A8C> /usr/lib/pam/pam_krb5.so.2
0x10fb37000 - 0x10fb3afff pam_opendirectory.so.2 (135.1) <2C62DFD6-E17E-3947-9596-3969D439F339> /usr/lib/pam/pam_opendirectory.so.2
0x10fbdd000 - 0x10fbe2fff com.apple.IOAccelerator (74.15 - 74.15) <D8C40179-4A29-3401-9B35-6E61EA278D41> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelera tor
0x10fbea000 - 0x10fbf6fff libGPUSupportMercury.dylib (8.10.1) <1DE2D7F9-C031-3BBF-BD5F-4E1208B6F296> /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/lib GPUSupportMercury.dylib
0x10fc02000 - 0x10fc0bfe7 libcldcpuengine.dylib (2.2.16) <B6E3B14B-1EAC-3FDD-8AED-87231A033BED> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengin e.dylib
0x110e4e000 - 0x110e62fff com.apple.DisplayServices (2.7.2 - 357) <523E7F24-1DB4-3898-8DAB-4A809F03C445> /System/Library/LoginPlugins/DisplayServices.loginPlugin/Contents/MacOS/Display Services
0x110e74000 - 0x110e7bfff com.apple.DFSLoginPlugin (2.3 - 2.3) <49317E74-9FC6-323D-8CD1-26E1EFBECF04> /System/Library/LoginPlugins/FSDisconnect.loginPlugin/Contents/MacOS/FSDisconne ct
0x110ef9000 - 0x110f26ff7 com.apple.BezelServices (237.2 - 237.2) <C6D587A2-3433-3B70-A0C5-372337877D82> /System/Library/LoginPlugins/BezelServices.loginPlugin/Contents/MacOS/BezelServ ices
0x110f3e000 - 0x110f43fff com.apple.BezelServicesFW (237.2 - 237.2) <23497F21-5621-3CB4-8350-3EAC86BA000E> /System/Library/PrivateFrameworks/BezelServices.framework/Versions/A/BezelServi ces
0x110f4a000 - 0x110f4cfff com.apple.framework.machinesettings (11.0 - 11.0) <B26DDE52-4495-3B0B-9602-8CC65F764646> /System/Library/PrivateFrameworks/MachineSettings.framework/Versions/A/MachineS ettings
0x110f52000 - 0x110f5fff7 com.apple.iokit.IOHIDLib (1.8.1 - 1.8.1) <59A22950-7AC0-349F-89F1-1196B44BF296> /System/Library/Extensions/IOHIDFamily.kext/Contents/PlugIns/IOHIDLib.plugin/Co ntents/MacOS/IOHIDLib
0x110f8e000 - 0x110fb9fff GLRendererFloat (8.10.1) <055EC8E7-2D7E-370C-96AD-DBEEDB106927> /System/Library/Frameworks/OpenGL.framework/Resources/GLRendererFloat.bundle/GL RendererFloat
0x110ff0000 - 0x110ff4fff com.apple.ServerInformation (1.2 - 1) <5AC80E5E-3B55-3784-854D-1D49A874E775> /System/Library/PrivateFrameworks/ServerInformation.framework/Versions/A/Server Information
0x1116be000 - 0x1116beff9 +cl_kernels (???) <46B442A3-E70F-4BDE-B1B4-C622D1D9C3E3> cl_kernels
0x113155000 - 0x113155ff1 +cl_kernels (???) <20B83F0C-677B-494B-9F55-258CE5E4E743> cl_kernels
0x113bec000 - 0x113daafff GLEngine (8.10.1) <1BD4D913-CE6C-3389-B4E1-FC7352E4C23F> /System/Library/Frameworks/OpenGL.framework/Resources/GLEngine.bundle/GLEngine
0x113de1000 - 0x113f51fff libGLProgrammability.dylib (8.10.1) <3E488CEF-5751-3073-B8EE-0B4CA39CB6AB> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgramma bility.dylib
0x113f89000 - 0x11440aff7 com.apple.driver.AppleIntelHD5000GraphicsGLDriver (8.16.76 - 8.1.6) <6BD6CE4E-681E-3242-8463-B3C9D919EDA0> /System/Library/Extensions/AppleIntelHD5000GraphicsGLDriver.bundle/Contents/Mac OS/AppleIntelHD5000GraphicsGLDriver
0x115277000 - 0x11530dff7 unorm8_rgba.dylib (2.2.16) <853BEBC4-AED9-3CE2-B91D-3D666E7C7C8F> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/ImageFormats/u norm8_rgba.dylib
0x11532c000 - 0x1153c6ff7 unorm8_bgra.dylib (2.2.16) <5D62BED8-DF5D-3C51-94B4-57368FF10DDB> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/ImageFormats/u norm8_bgra.dylib
0x1156ca000 - 0x1156cffff com.apple.audio.AppleHDAHALPlugIn (2.4.7 - 2.4.7fc4) <EA592C9E-AD15-3DD0-85BE-D47BBBE04286> /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bun dle/Contents/MacOS/AppleHDAHALPlugIn
0x7fff6f4c6000 - 0x7fff6f4fa94f dyld (210.2.3) <8958FE97-5830-3928-BC38-23136E7D3783> /usr/lib/dyld
0x7fff85c8b000 - 0x7fff85c8ffff libGIF.dylib (852) <326C48F1-C892-3AF9-94BC-32768EFF6731> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x7fff85c90000 - 0x7fff85ca6fff com.apple.MultitouchSupport.framework (237.4 - 237.4) <0F7FEE29-161B-3D8E-BE91-308CBD354461> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/Multit ouchSupport
0x7fff85ca7000 - 0x7fff85caefff libcopyfile.dylib (89) <876573D0-E907-3566-A108-577EAD1B6182> /usr/lib/system/libcopyfile.dylib
0x7fff85caf000 - 0x7fff85cbaff7 com.apple.bsd.ServiceManagement (2.0 - 2.0) <C12962D5-85FB-349E-AA56-64F4F487F219> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManage ment
0x7fff85cbb000 - 0x7fff85d61ff7 com.apple.CoreServices.OSServices (557.6 - 557.6) <E91B0882-E75C-30E9-8DCD-7A0EEE4405CC> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x7fff85d62000 - 0x7fff85d87ff7 libc++abi.dylib (26) <D86169F3-9F31-377A-9AF3-DB17142052E4> /usr/lib/libc++abi.dylib
0x7fff85d88000 - 0x7fff85d8afff libCVMSPluginSupport.dylib (8.10.1) <F0239392-E0CB-37D7-BFE2-D6F5D42F9196> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginS upport.dylib
0x7fff85d8b000 - 0x7fff85dceff7 com.apple.bom (12.0 - 192) <0BF1F2D2-3648-36B7-BE4B-551A0173209B> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
0x7fff85e2a000 - 0x7fff85e52fff libJPEG.dylib (852) <4E159C31-1B41-3EFF-89EC-3F7BC9053F2C> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x7fff85e53000 - 0x7fff85fa5fff com.apple.audio.toolbox.AudioToolbox (1.9.2 - 1.9.2) <DC5F3D1B-036A-37DE-BC24-7636DC95EA1C> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x7fff85fee000 - 0x7fff863e5fff libLAPACK.dylib (1073.4) <D632EC8B-2BA0-3853-800A-20DA00A1091C> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
0x7fff86449000 - 0x7fff86466ff7 com.apple.openscripting (1.3.6 - 148.3) <C008F56A-1E01-3D4C-A9AF-97799D0FAE69> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting .framework/Versions/A/OpenScripting
0x7fff86467000 - 0x7fff864a2fff com.apple.LDAPFramework (2.4.28 - 194.5) <7E4F2C08-0010-34AE-BC46-149B7EE8A0F5> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP
0x7fff8654d000 - 0x7fff8655bfff libcommonCrypto.dylib (60027) <BAAFE0C9-BB86-3CA7-88C0-E3CBA98DA06F> /usr/lib/system/libcommonCrypto.dylib
0x7fff8655c000 - 0x7fff86570fff com.apple.speech.synthesis.framework (4.1.12 - 4.1.12) <94EDF2AB-809C-3D15-BED5-7AD45B2A7C16> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x7fff86571000 - 0x7fff86572fff libDiagnosticMessagesClient.dylib (8) <8548E0DC-0D2F-30B6-B045-FE8A038E76D8> /usr/lib/libDiagnosticMessagesClient.dylib
0x7fff8658d000 - 0x7fff8660cff7 com.apple.securityfoundation (6.0 - 55115.4) <9291CE2A-37D9-39DF-956E-7B2650A9F3B0> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoun dation
0x7fff8663a000 - 0x7fff8663bfff liblangid.dylib (116) <864C409D-D56B-383E-9B44-A435A47F2346> /usr/lib/liblangid.dylib
0x7fff8663c000 - 0x7fff8667dff7 com.apple.framework.corewlankit (2.0.2 - 202.11) <5B9D1E57-DA1D-3BF3-BB4E-87D4AF28A919> /System/Library/PrivateFrameworks/CoreWLANKit.framework/Versions/A/CoreWLANKit
0x7fff8667e000 - 0x7fff8674aff7 libsystem_c.dylib (825.40.1) <543B05AE-CFA5-3EFE-8E58-77225411BA6B> /usr/lib/system/libsystem_c.dylib
0x7fff86774000 - 0x7fff8680efff libvMisc.dylib (380.10) <A7F12764-A94C-36EB-88E0-F826F5AF55B4> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
0x7fff868c0000 - 0x7fff868c4ff7 com.apple.CommonPanels (1.2.5 - 94) <AAC003DE-2D6E-38B7-B66B-1F3DA91E7245> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels. framework/Versions/A/CommonPanels
0x7fff86900000 - 0x7fff8699eff7 com.apple.ink.framework (10.8.2 - 150) <3D8D16A2-7E01-3EA1-B637-83A36D353308> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
0x7fff8699f000 - 0x7fff86a07ff7 libc++.1.dylib (65.1) <20E31B90-19B9-3C2A-A9EB-474E08F9FE05> /usr/lib/libc++.1.dylib
0x7fff86a66000 - 0x7fff86b71fff libFontParser.dylib (84.6) <96C42E49-79A6-3475-B5E4-6A782599A6DA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Resources/libFontParser.dylib
0x7fff86b72000 - 0x7fff86b79fff libGFXShared.dylib (8.10.1) <B4AB9480-2CDB-34F8-8D6F-F5A2CFC221B0> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.d ylib
0x7fff86b7a000 - 0x7fff86b7dff7 libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib
0x7fff86b7f000 - 0x7fff86e96ff7 com.apple.CoreServices.CarbonCore (1037.6 - 1037.6) <1E567A52-677F-3168-979F-5FBB0818D52B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x7fff86e97000 - 0x7fff87827627 com.apple.CoreGraphics (1.600.0 - 333.1) <C085C074-7260-3C3D-90C6-A65D3CB2BD41> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
0x7fff87828000 - 0x7fff87874ff7 libauto.dylib (185.4) <AD5A4CE7-CB53-313C-9FAE-673303CC2D35> /usr/lib/libauto.dylib
0x7fff87875000 - 0x7fff87b46ff7 com.apple.security (7.0 - 55179.16) <BD03EB7E-1745-34B9-8DBA-7A2215D9F2FB> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x7fff87b47000 - 0x7fff87c21fff com.apple.backup.framework (1.4.3 - 1.4.3) <6B65C44C-7777-3331-AD9D-438D10AAC777> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup
0x7fff87c22000 - 0x7fff87c73ff7 com.apple.SystemConfiguration (1.12.2 - 1.12.2) <581BF463-C15A-363B-999A-E830222FA925> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x7fff87c74000 - 0x7fff88091fff FaceCoreLight (2.4.1) <DDAFFD7A-D312-3407-A010-5AEF3E17831B> /System/Library/PrivateFrameworks/FaceCoreLight.framework/Versions/A/FaceCoreLi ght
0x7fff88092000 - 0x7fff88092ffd com.apple.audio.units.AudioUnit (1.9.2 - 1.9.2) <6D314680-7409-3BC7-A807-36341411AF9A> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x7fff88093000 - 0x7fff88190fff libsqlite3.dylib (138.1) <ADE9CB98-D77D-300C-A32A-556B7440769F> /usr/lib/libsqlite3.dylib
0x7fff88191000 - 0x7fff881caff7 libssl.0.9.8.dylib (47.2) <46DF85DC-18FB-3108-91F6-52AE3EBF2347> /usr/lib/libssl.0.9.8.dylib
0x7fff881cb000 - 0x7fff881d9ff7 libkxld.dylib (2050.48.12) <B8F7ED1F-CF84-3777-9183-0A1C513DF81F> /usr/lib/system/libkxld.dylib
0x7fff88217000 - 0x7fff88217fff com.apple.Cocoa (6.7 - 19) <1F77945C-F37A-3171-B22E-F7AB0FCBB4D4> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x7fff882cc000 - 0x7fff882daff7 libsystem_network.dylib (77.10) <0D99F24E-56FE-380F-B81B-4A4C630EE587> /usr/lib/system/libsystem_network.dylib
0x7fff8863d000 - 0x7fff8899cfff com.apple.Foundation (6.8 - 945.19) <C98E55BA-553B-314B-B056-849FFB20C220> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff8899d000 - 0x7fff889d7ff7 com.apple.GSS (3.0 - 2.0) <423BDFCC-9187-3F3E-ABB0-D280003EB15E> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
0x7fff889d8000 - 0x7fff88af8fff com.apple.desktopservices (1.7.4 - 1.7.4) <ED3DA8C0-160F-3CDC-B537-BF2E766AB7C1> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
0x7fff88af9000 - 0x7fff88b1bff7 libxpc.dylib (140.43) <70BC645B-6952-3264-930C-C835010CCEF9> /usr/lib/system/libxpc.dylib
0x7fff88b1c000 - 0x7fff88b1cfff com.apple.vecLib (3.8 - vecLib 3.8) <6CBBFDC4-415C-3910-9558-B67176447789> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x7fff88b1d000 - 0x7fff88b30ff7 com.apple.LangAnalysis (1.7.0 - 1.7.0) <2F2694E9-A7BC-33C7-B4CF-8EC907DF0FEB> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
0x7fff88b31000 - 0x7fff88b7aff7 com.apple.DiskManagement (5.3.1 - 680) <5438A1FF-B92C-3D28-A8E4-FB41F03144C2> /System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/DiskManag ement
0x7fff88f12000 - 0x7fff88f12fff com.apple.Accelerate (1.8 - Accelerate 1.8) <878A6E7E-CB34-380F-8212-47FBF12C7C96> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x7fff88f70000 - 0x7fff88fbcfff com.apple.framework.CoreWLAN (3.4 - 340.18) <3735FB49-30C0-3B11-BE25-2ACDD96041B5> /System/Library/Frameworks/CoreWLAN.framework/Versions/AIs this only happening in Firefox?
Sounds that a screensaver is kicking in. -
Color problems in photoshop cs5 and bridge
Recently, whenever I open images in photoshop or view them in Bridge, they look desaturated. In Bridge, they load normal at first but after a couple of seconds, they become desaturated and I can't figure out what the problem is. I have all of the same color management settings as before, the only difference on my computer since the colors stopped working was that my computer installed windows updates. The images look fine when viewing them in the Windows viewer, and in other programs like ACDSee, etc. It only looks like this in Adobe programs. I checked in Bridge under Creative Suite color settings, and it is under North America General Purpose 2. In Photoshop, I checked color settings, and all of them are marked as convert to working rgb, cmyk, etc. Any suggestions?
The monitor color profile tells Photoshop and the other color managed programs how your monitor displays colors. Color profile files are installed by putting them in C:\Windows\System32\spool\drivers\color. Then to assign or confirm a color profile for your monitor, you use the Color Management control panel. Under the Devices tab when 'Use my settings for this device" is checked, the color profile currently in used is the one which name ends with (default). For example 'Dell U2410 color Profile, D650 (default)'.
You can download the color profile for you monitor from here http://support.dell.com/support/downloads/download.aspx?releaseid=R279694&formatcnt=0&libi d=0&fileid=413637
http://support.dell.com/support/downloads/download.aspx?releaseid=R279694&formatcnt=0&libi d=0&fileid=413637
it downloads a .exe file which is simply a decompressor like .zip files. Run it, and in the folder you will find a file with the name DELL-U2410.icm - his is your monitor color profile from Dell. However most likely Windows has already installed it for you.
Now, given your situation, you may have these eventual problems.
First problem.
Your monitor is a wide gamut monitor 102% of NTSC and Windows defaults at sRGB which is about 70% fo NTSC. NTSC is a color space representing the visible spectrum and is used in monitor specs for measuring the gamut.
Assuming that for some time you didn't use a color profile which more closely represents your monitor, Photoshop was displaying images on your wide gamut monitor using the default sRGB color profile which represent standard gamut sRGB monitors and this is very different from yours. Said in other words you were seeing one thing on your monitor while Photoshop was assuming it is another thing. This becomes a problem when you convert from one color space to another and display or reproduce the image on other devices, and in your case when monitor profile is changed to a very different one. To fix this you have to assign your correct monitor profile to the images that were created with the wrong profile and then convert to a common color space like sRGB, AdobeRGB, etc. Assign and Convert to profiles are in the Edit menu.
Second problem.
The color profile from Dell may not be representing correctly how your monitor displays colors. Dell creates a profile that is not measured to your particular unit but for what they assume is an average representation of the monitor's model. Using it, you depend entirely on luck. I have u2711 and I was very unlucky. If you are curious you can study my case which may be also very educational for you and will be able to see clearly the difference between the colors of my monitor and those the Dell color profile represents. Follow the same instructions above for downloading the color profile for your monitor but download the one for u2711 from here
http://support.dell.com/support/downloads/download.aspx?releaseid=R247058&formatcnt=1&libi d=0&fileid=365277
then go to that web site from your link http://www.tftcentral.co.uk/articles/icc_profiles.htm and download my color profile that I'm sharing there. It is 'Dell U2711 Spyder 3 + Color Eyes DP User' once you have the color profiles files on you computer, go to this site http://www.iccview.de/content/view/3/7/lang,en/ , upload my monitor profile and the one from Dell and compare. That web site will give a 3D plot of two color spaces in a 3D viewer that you can navigate to see it from all sides (using the Ctrl, Shift navigates faster). The difference that you see made it impossible to create even simple images for the web using Photoshop. I convert from AdobeRGB to sRGB and when Photshop assumes that my monitor displays colors the way they are described in the Dell's profile, all detail in the shadows is eliminated and my images look like crap. I even got better results from creating a profile using this free software http://www.calibrize.com/ it uses the so call eyeometer relying on your eyes for feedback and although the colors were noticeably off, at least the shadow detail was preserved.
Hope that helps -
I imported tiff images into Lightroom 4 that were scanned by DigMyPics.com. The color of the images look good on the Windows 7 photo viewer. It looks horrible in Lightroom 4. My monitor is callibrated, the import develope setting is set to "none" , the box is unchecked "apply auto tone adjustments". I think that the windows viewer is showing the accurate color of the scan and LR is not. I don't think DigMyPics would send this awful color. What could the issue be?
monitor NEC 2690 wuxi
eye-one display 2
Original message
From: twenty_one
To: [email protected]
Received: 2/10/2013 12:30:42 PM
Subject: lightroom 4 color problem
Re: lightroom 4 color problem
created by twenty_one in Photoshop Lightroom - View the full discussion
Yes, that certainly looks like a problem with the Lightroom rendering. Skin tones and red in general is clearly off, while Windows Photo Viewer looks good.
I'm almost certain this is a problem with the monitor profile. As troubleshooting, try to set sRGB as monitor profile (or Adobe RGB if your monitor is wide gamut), and see if the difference persists. But try to recalibrate first.
What calibrator and what monitor?
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/5062403#5062403
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/5062403#5062403
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/5062403#5062403. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Photoshop Lightroom by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746. -
Touchsmart monitor colors suddenly reverse
A few days after the trial period for Windows 8 expired I booted up to find that the monitor colors were reversed. What was black was now white, etc. I thought it was something Microsoft had done to provoke me to hurry up and buy 8, but after removing 8 and installing Linux Mint the problem continued. Someone suggested that it might be the video card since, they claim, Touchsmarts tend to cause the video card to overheat. Has anyone had this problem and how was it solved?
The model is IQ504Hello Eljey,
Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More. I have read your post on how the screen on your Touchsmart displays colors in reverse, and I would be happy to assist you! To begin, I will need to ask you a few questions:
Has your computer completed all of its important Windows Updates?
Have you updated your HP drivers using the HP Support Assistant?
Is this an on-going, or recent issue?
In the meantime, I recommend following this document on Display Quality Issues. This should help the discoloration displayed on your screen.
Please re-post with the results of your troubleshooting, as well as the requested information above. I look forward to your reply!
Regards
MechPilot
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping! -
Monitor Colors wrong following a re-install of 10.3
I've fixed this once, a year ago, but have forgotten how!
I have had to re-install 10.3 due to some other problems but with this fresh system, the monitor colors are not quite right. For example, the finder icon in the dock is purple, the label colors are all wrong, not only in color but have blocks of different color in them.
I've messed with display preferences but cannot fix it. As I said this happened when I upgraded to 10.3 from 10.2.8 a year ago and I fixed it. Looking at the display preferences on the system where the color is OK and this one, I can see no difference. Calibrating the monitor did not seem to help.
Any ideas appreciated.I haven't had this exact problem but on a couple of occasions, when my normal user setup wasn't behaving quite correctly, I started up from a new account, copied the preferences (HD/Users/UserAccount/Library/Preferences) to a new folder at the root level of my hard drive, restarted as my standard user, then used the preferences from the new account to overwrite those in my standard account. Sometimes you won't be able to overwrite them because they are in use; then just move the ones that can't be replaced to the trash, move the new ones to your user account preferences folder, restart and empty the trash.
Hope this works for you. -
I created a design in Fireworks CS5 and everything looks correct. I'm used to Fireworks when it comes to color, ie Fireworks just shows the monitor colors and that's it, no color profiles or proof colors or anything.
So I save as PSD and open in Photoshop, and in Photoshop everything looks really washed out. If I set the View > Proof Setup to Monitor RGB everything looks extremely oversaturated.
I have two montiors and they both exhibit the same problem but to different extents.
Anyone have any tips?
Thanks.
- AaronI did actually have a custom monitor profile, not using a calibration device but just some eye-tuning wizard in windows 7.
"you can simply turn off color management completely in the color prefs."
That's definitely what I would like. By this do you mean Edit > Color Settings -- Settings: Monitor Color? I've done this now and removed the calibration profile, and now things look correct, thanks. Unfortunately now things look awful in Windows Photo Viewer, everything is very blown out. Any idea why this would be? -
I have calibrated my Dell monitor with EyeOne Display 2. The profile created by the EyeOne Display 2 is in the standard location "C:\WINDOWS\system32\spool\drivers\color". This profile has been set as the default profile for the monitor.
I edit from RAW pictures in LR. Once I am satisfied with the colors, then exported pictures to JPEG using SRGB profile and the "EyeOneXXX.icc" profile calibrated using EyeOne Display 2.
The pictures that got exported using "EyeOneXXX.icc" when viewed in a color management enabled FireFox browser look identical to what I see in the Lightroom. The pictures that got exported using "SRGB" has little less saturation when viewed in color management enabled Firefox browser than that looks in the LightRoom. What is the reason for this difference.
Usually how should I export i.e. should I export to SRGB or monitor calibrated profile when I need to send them to print at Costco.
Also, Costco has their printer profiles online. Should we use it soft proof it or should we use it when exporting to JPEGs in LR.
Thanks
Chandra
Software: LightRoom 2.3
OS: Windows Vista Home Premium
Monitor: Dell (Connects HP laptop to this monitor during editing)
Calibration: EyeOne Display 2
Camera : Nikon D90
Lens: Nikon 18-105mm that comes with Nikon D90What do you mean by "I should use standard color profile SRGB"? Do you mean that I should use SRGB as color profile in LR when exporting to JPEG.
I calibrated my 19 inces Dell monitor connected to my latop using Eyeon display 2. The options I have used while calibrating are "Native WHite, Gama 2.2" My monitor color temperature is set 5000K. The profile created by calibration is used as the default color managment profile for the monitor.
Also why is the following problem happening.
I usually edit RAW photos in LR in a calibrated monitor as per info. given in the signature. After editing, I exported photos using SRGB and "EyeOneXXX.icc" i.e. Calibrated Monitor profile.
I printed the pictures in Costco. The photos with SRGB have redish cast. The photos exported using Monitor profile are under saturated than the photos I see in the Lightroom.
If I load the photo exported using monitor profile in CS3 and select "View -> Proof Setup -> Windows RGB", the picture show in CS3 under these conditions are similar to the prints at Costco i.e. lot under saturated. If I select "View -> Proof Setup -> Monitor RGB", the picture looks like in LR.
If I load the photo exported using SRGB profile in CS3 and select "View -> Proof Setup -> Windows RGB", the photo looks like in LR. If I select "View -> Proof Setup -> Monitor RGB", the picture looks like the prints at Costco i.e. lot over saturated.
In CS3 on the monitor the photos under the following two conditions are identical:-
1. Photo exported using monitor profile and the proof setup option in CS3 is "View -> Proof Setup -> Monitor RGB"
2. Photo exported using SRGB profile and the proof setup option in CS3 is "View -> Proof Setup -> Windows RGB"
I even soft proofed the Costco Printer profiles. The corresponding photos viewed under costco print profile is almost identical to the photos seen in the 1 and 2 options described above.
I basically want the photos to look like what I see in LR. From the above information what could be the problem I am having i.e. why are my printed photos does not look like in LR.
Thanks
Chandra -
****yellowish color shift in LIGHTROOM: disabling monitor color profile in LR?
Hi all,
I would love to know if there is a way to ***disable the monitor (color) profile**** in LR.
WHY?
Cause all my pictures seems yellowish in LR, and not anywhere else (firefox, i.e, photoshop, xnview, etc...)
I solved the same problem in PHOTOSHOP, this way :
when loading images in photoshop, during starting up, I got this very message :
" The monitor profile 'LG L245WP' appears to be defective. Please rerun your monitor calibration software. "
with two possible options :
"Ignore profile" or "use anyway"
Then if I use "Ignore profile" everything is fine!
If I select "use anyway" --> Wrong, all my pictures are yellowish.
That's why I WOULD LOVE TO KNOW, pleaaaaaase if I can do the same in LR.
I personnally didn't find, or what else I should do ?! Knowing that I do not have a ...too expensive!... calibration tool , and my monitor is a LG, L245WP.
----> Thanx sooo much for your help.
I would love to use LR, but this way I can't...
>kiwiii
form PARIS france ( excuse my english level).
NB : I read 2 threads here , but didn't find my solution : http://forums.adobe.com/thread/414524
and : http://forums.adobe.com/thread/415180
NB : in one of these I downloaded this RGB picture :
http://forums.adobe.com/servlet/JiveServlet/download/2161301-16291/Farbprofil-Kontrolle_re dgreenblue.jpg
where mostly the white in LR appears to be yellow.
Looks fine anywhere else, and in photoshop, if "Ignore profile" is selectedDdeGannes, Sean : thanx.
I went to my vista profil , added a profile in relation with my screen... but then which on should I select , between the several sRGB options :
- WCS profile : sRGB a file named wsRBG.cdmp
or
- ICC profile : sRGB IEC 61966-2.1 ?
( of course I have many more... but....none of the others are sRGB profiles )
Then have you both a calibrator, and you both did all the color "chain" from CAMERA to PRINTER ?
I am asking.... cause all these adjustments + buying a calibrator seems tough to me to manage/achieve.
You know : I'm not a professional ...
To me, non - pro, it looks even more dangerous to do so than leaving evreything in default mode & presets...
Should I do something wrong...
NO?
Moreover I mean : this is odd that my computer , or/AND (?) screen ,
doesn't have a "default setting" which would be suitable in LR , at least which no colour shift !
( I just change my LG screen mode to 5600K etc... and still I have the same yellowish gap in LR )
Why would my color management just be wrong in LR or Photoshop ?
Doesn't this light something I miss to you both, maybe professionals?
If I read you fine, + the other website... everything is kind of automatic now in every softwares... even xnview, firefox, (not i.e.) etc...
so why just LR + photoshop, would be mistaken on my computer,
and Firefox, Xnview, CANON softwares, Painter, ... all show the right profile & colors ???? This is sooooooo weird....to me.
I mean I got the the point that my whole color management is unshure...
but it nevertheless it should BE THE SAME through all my softwares... NO ?
Isn't there a general ADOBE setting somewhere, that might be bugged instead?
I still think , according to that, that we are missing something.
Sorry to bother you with my thoughts....
kiwiii ( paris - france )
ps/ Does really Photoshop detect the changes I would do directly on my screen ?
Because when I switch from sRGB, to 6500 K , 9300K or user... on my screen,
I STILL HAVE the PHOTOSHOP ERROR message :
" The monitor profile 'LG L245WP' appears to be defective. Please rerun your monitor calibration software. "
I mean PHOTSHOP doesn't seem to notice (give a damn) on any change I make !?
As for the rest of my computer I never changed any COLOR PROFILE anywhere... So how do people do without a calibrator to use LR ?
Is it possible at least?
Is my screen (i thought so good) totally bugged, if none of my color profile is "ok" for photoshop & LR ?
THANX AGAIN FOR READING and helping me... -
Color problems between Lr5 and other software
I can not see where to make adjustments to get the same tones between Lr and my other software: Photoshop, Irfanview, Windows Viewer ...
My test conditions:
My monitor is calibrated
... - Export Lr Jpeg quality 85% and also tests 16bit TIFF (sRGB, Adobe rgb and prophoto)
... - When exporting, I checked the "add to catalog" to view the same image in Lr.
Conclusion: Other software gives almost the same tones (some small differences due to the chosen color space) and Lr gives a much warmer picture (Raw or treated Jgeg reimported in the catalog). Will it have a preference of Lr to settle?
Note: the direct opening of RAW file in Photoshop with Camera Raw (same engine as Lr) without special settings, also gives a duller color different image, that directly Lr.
What is the solution?In general, any difference between Lightroom and other color managed software is indicative of a corrupt monitor profile. No idea about Irfanview, but Lightroom, Photoshop and Windows Photo Viewer should all display identically.
What they all do is convert from the source/document color space to the target color space, which for display is your monitor profile. The result should be identical - that is in fact the whole point of color management. But since the source space may be different the actual conversion itself may also be different. So one conversion may go bad but not others.
A difference between Library and Develop will have the same explanation (different source spaces; Library is Adobe RGB while Develop is linear ProPhoto).
It also happens that different applications react differently to a bad monitor profile. It may work in one application and fail in others.
Any software that is not color managed will simply display in the native monitor color space, which can be anything under the sun, so you can just ignore and disregard that. It won't be accurate anyway.
So the solution is to have a valid and healthy monitor profile. Then everything color managed will display identically (save for gamut differences, but in practice that only applies if you have a wide gamut monitor. With a standard monitor any source space will have equal or larger gamut than the monitor).
Some calibration software has been known to not follow specifications strictly at all times, so check for updated software. Or the profile can simply have become corrupt. It happens. A way to test this is to set sRGB as default monitor profile in the OS - or Adobe RGB if you have a wide gamut monitor - and see if the problem clears. -
Epson 2200 Color problem solved...I think
I have read the posts on the color problems with 10.6 and the EP 2200. I too had the same issues after installing 10.6 this evening. After much teeth grinding and some choice words I set about solving my printing problem.
The Gutenprint driver has the same problems GIMP had. It isn't really printer specific, as in all the options you once had. I would rather have no driver than have this lame piece of software automatically installed. Gutenprint will make the printer run but that's about all it will do.
The solution is pretty easy:
1. Open System Preferences. Click on Print and Fax
2. Select the 2200 (or any printer giving you fits) and click the to delete the printer. Close prefs.
3. Go to the Epson site and download the 10.4 driver, Epson 11832. Install.
4. Also download the 10.6 updater and install.
5. Open System Prefs>Print and Fax again.
6. Click the and select the printer model, in my case Epson 2200.
7. In the drop down window Select Epson SP 2200 not the Epson Stylus Photo 2200 - Gutenprint v5.2.3! The latter being a Jack of all Trades and Master of none.
8. All the print functions reappear as expected.
Do I believe the reports of Epson dumping on the Mac market? Not a chance. Mac has the majority (well over 50% and growing) of the graphic and creative arts market. Most professional photographers I know use the Mac platform and are very enthusiastic about it. Epson couldn't afford to turn their backs on the Mac platform.
With 10.6 I did loose all my custom icc profiles from PS but not PS Lightroom. I also lost the custom monitor profile. I will re-profile my paper/ink/scanner/monitor and consider it a light hit. I'm sure I don't know why this update was so rough on the drivers. I'm also sure that there will be other pains I have yet to discover.
Is 10.6 crap? Probably not. Will I install 10.7 when it arrives? You bet! At OSX worst it is better than Gate's best!!This is all good info, but for me at least, the real issue is not whether you can get the driver/printer to function (most people seem to be able to get it working) but when you get it functioning under Snow Leopard are there color issues.
Although the printer may work fine for basic documents etc, it is for color-critical photo work that I need my 2200. Many other posts are reporting that although the driver is functioning, there are fairly severe color issues when trying to create high-quality photographic prints using the standard color-managed workflow. This would be rather crippling for photographers and other artists who rely on their 2200.
Maybe those posting here could comment on whether they have been using their 2200 for photographic purposes and whether or not they have seen color issues. I wonder if some people just aren't noticing a problem because they aren't doing color-managed photographic work.
I haven't installed Snow Leopard yet and I'm trying to determine if this is affecting a very small percentage of people or if everyone is having trouble getting proper color from their 2200 since Snow Leopard. So far I haven't seen a single post specifically stating that they they are using the 2200 for high quality photo printing and have had no color issues under Snow Leopard.
Message was edited by: Bazzography -
Aperture 2.0 second display color problem ... possible bug
Hi, I am running a Macbook pro 2.4 with a Formac 2010 as the second monitor.
Both monitors are calibrated with an Eyeone display and coloreyes software.
Since installing the aperture 2.0 trial my Formac monitors colors are off.
Colors on the Macbook pro are perfect, but the Formac has to much red in it (peoples faces have a yellow orange tint and reds and oranges are over-saturated)
I have tried re-calibrating 8 times, with various settings (standard is d65, gamma 2.2, 120 luminence on both monitors, with no joy.
I did not have this problem with Aperture 1.5.6, colors were a perfect match.
I have tied reinstalling Aperture 2.0, deleting all preferences and starting again ... still no luck.
If i export an image to Photoshop, the colors match the macbook pro screens perfectly (when viewed on the Formac display)
I can even drag the exported image in photoshop to the second screen in Aperture and view them one over the other. Result ... the photoshop image looks fine but the Aperture image is over saturated...and that's on the same monitor at the same time.
Next i reverted back to Aperture 1.5.6.. guess what, all colors match on both screens.
I can only think that there is a bug in aperture 2.0, what else can it be?
Can anyone help me out, i am loving 2.0 but if i cannot view the colors correctly then it is no good to me.
Thanks
MikeCOPIED FROM DP FORUMS
mikey1 wrote:
Just to clarify, the colors on my macbook pro are perfect, it is the
formac second monitor that has the color shift problem.
I understand the colours look bad on your Formac
Aperture 2.0 is not recognizing the second monitors color profile
So what profile do you suspect it is using?
As this is the monitor i mostly work on (better gamutt etc) it is a
problem.
My workaround is to shut the laptop lid and work solely from the
formac monitor.
My guess is its using the MBPs profile for both the MBP and the Formac which is why it looks bad. So if you load the Formac profile to the MBP, maybe it will use the Formac profile for both the MBP and the Formac. Yes, the MBP will get bad colour, but the Formac may get it's good colour back. Then at least you could navigate on the MBP screen and edit on the Formac screen, rather than having to close the MBP screen. I'm not saying it will work, but I would give it a try as a work around.
-Najinsky
Genius .... spot on Najinsky
Did as you suggested and it worked.
Formac monitor is definitely using the macbook pro profile.
Exported an image to cs3, then dragged it back over the fullscreen aperture version and hey presto.... exact color match.
So many thanks for your help
Now, why am i the only one to notice this, all i need is a few more bods to have the same issue and then i can sit back and wait for apple to sort it.
If i am the only person with this problem, then what is wrong.
I just ran diskwarrior in a last ditch attempt to see if i have something amiss on my system.. still no luck.
Come on people, how are you getting on with your second monitors?
Could it be to do with the pro app updates?
Any ideas on my next move.
Heres hoping
Maybe you are looking for
-
My ipad mini 2 is not turning on. I tried to reset with the power/home buttons but it didnt work. I tried to restore it in DFU mode but it didnt work, i get error 4004. Please help me!
-
Hello I recently tried to upgrade the hard-drive in my macbook pro 2010 13". I backed up the old drive using SuperDuper to my external drive. I replaced the original internal hard-drive with my newly purchased Western Digital Scorpio blue 1Tb 5400rpm
-
Cant print in color with R2880 - Only B
Hi everyone, I have an Epson R2880 running on Windows 7 pro. I turned off color management in control panel printer driver. In Adobe Lightroom 5.6 i checked SPR2880 premium luster. I've tried jpeg and nef file and i can only print in black and whit
-
Getting access to my old iPod without resetting it
I recently found my old iPod 3, and I forgot the password to it but I'd really like to get access to it again. Is there any way this is possible or do I have to reset it?
-
CRM standard Business objects reports or dashboard content to enable
Hi Can anyone provide the inputs on availability of standard Business objects reports or xcelsius dashboards in CRM as content. How to activate and use them. (not the BI content).