Re: __CGPixelAccessLockWindowAccess???
Re: __CGPixelAccessLockWindowAccess???
- Subject: Re: __CGPixelAccessLockWindowAccess???
- From: Stephane <email@hidden>
- Date: Thu, 21 Jun 2007 19:54:01 +0200
On Jun 21, 2007, at 7:45 PM, David Duncan wrote:
On Jun 21, 2007, at 10:30 AM, Stephane wrote:
What can be the reason for the following warning in console.log:
__CGPixelAccessLockWindowAccess: access lock failed: error 1001.
A quick search in Google shows that numerous applications have
seen this issue (including Apple's Software Update.app) but there
is no explanation.
Error 1001 indicates a bad argument was passed, so I would surmise
that it's a bad window (likely one that has already been disposed).
This might explain why when you close some combination of windows
it no longer occurs.
Unfortunately, I couldn't tell you where the bug is exactly without
a lot more spelunking. If you really want to know, then filing a
DTS incident would be appropriate.
I think I've found the origin of the bug. It's probably in the OS
frameworks as I don't think it's forbidden to do what I'm doing.
The specific thing about the window leading to this bug is that it
has a NSButton whose shortcut is set to \r. So the NSButton is
throbbing.
If no shortcut is set for the NSButton, there is no error (tried it
20 times). If the shortcut is set in the nib, there is an error
(first test produced the error).
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden