Lightroom "CGXDisableUpdate" error every time it starts

  • 1
  • Problem
  • Updated 6 years ago
I just noticed from my log (OS X 10.8.1) that every time I start Lightroom I get this error:

30/08/12 19:04:25,000 kernel[0] CODE SIGNING: cs_invalid_page(0x100000000): p=13356[AdobeCrashDaemon] clearing CS_VALID
30/08/12 19:04:29,280 WindowServer[143] CGXDisableUpdate: UI updates were forcibly disabled by application "Lightroom" for over 1.00 seconds. Server has re-enabled them.
30/08/12 19:04:29,706 WindowServer[143] reenable_update_for_connection: UI updates were finally reenabled by application "Lightroom" after 1.43 seconds (server forcibly re-enabled them after 1.00 seconds)


I'm running the 4.2 RC.
Please tell me if you need more data.
Photo of Paolo Avezzano

Paolo Avezzano

  • 58 Posts
  • 1 Reply Like

Posted 6 years ago

  • 1
Photo of Pete Green

Pete Green, Customer Advocate

  • 699 Posts
  • 126 Reply Likes
Have you tried resetting lightroom's preference file?

On Mac, you’ll find com.adobe.LightroomX.plist with the other Preferences files at Macintosh HD/Users/[your username]/Library/ Preferences/.

Quit Lightroom and move it to another folder, rename or delete it, and then restart Lightroom.
Photo of Paolo Avezzano

Paolo Avezzano

  • 58 Posts
  • 1 Reply Like
I noticed that is easy to trigger those errors: I'm comparing two version of the same image, zoomed to 100%. Trying to move along the entire image (fn + up/down arrows), the screen is not responding and log is polluted with warnings:

31/08/12 10:19:09,126 WindowServer[127]: CGXDisableUpdate: UI updates were forcibly disabled by application "Lightroom" for over 1.00 seconds. Server has re-enabled them.
31/08/12 10:19:12,601 WindowServer[127]: reenable_update_for_connection: UI updates were finally reenabled by application "Lightroom" after 4.47 seconds (server forcibly re-enabled them after 1.00 seconds)
31/08/12 10:25:36,601 WindowServer[127]: CGXDisableUpdate: UI updates were forcibly disabled by application "Lightroom" for over 1.00 seconds. Server has re-enabled them.
31/08/12 10:25:42,885 WindowServer[127]: reenable_update_for_connection: UI updates were finally reenabled by application "Lightroom" after 7.28 seconds (server forcibly re-enabled them after 1.00 seconds)
Photo of Paolo Avezzano

Paolo Avezzano

  • 58 Posts
  • 1 Reply Like
I launched several concurrent exports via Publish Services.
It seems that the UI thread is affected as I'm unable to load Lightroom UI while other opened Apps are slow but responsive.

31/08/12 11:53:07,552 WindowServer[127]: disable_update_likely_unbalanced: UI updates still disabled by application "Lightroom" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.
31/08/12 11:53:20,743 WindowServer[127]: reenable_update_for_connection: UI updates were finally reenabled by application "Lightroom" after 28.18 seconds (server forcibly re-enabled them after 1.00 seconds)
31/08/12 11:53:41,488 WindowServer[127]: disable_update_likely_unbalanced: UI updates still disabled by application "Lightroom" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.
31/08/12 11:54:47,337 WindowServer[127]: reenable_update_for_connection: UI updates were finally reenabled by application "Lightroom" after 80.82 seconds (server forcibly re-enabled them after 1.00 seconds)
Photo of Paolo Avezzano

Paolo Avezzano

  • 58 Posts
  • 1 Reply Like
Deleted preferences and renamed Lightroom.
Same error log, just different time values on the third row of the message each time I reload Lightroom.
Photo of jdv

jdv, Champion

  • 728 Posts
  • 55 Reply Likes
CGXDisableUpdate is probably normal. This is just an ordinary log message that a lot of apps will trigger.

The code signing messages are a result of the new code signing stuff in 10.8. My guess is that Adobe didn't follow the byzantine rules necessary for any process they might start.

None of these messages are really significant in terms of Lightroom working. Some helper processes aren't playing by the new strict rules. The UI went to update the window server and then stopped for some reason.

Nothing serious.
Photo of Paolo Avezzano

Paolo Avezzano

  • 58 Posts
  • 1 Reply Like
John, frankly I find your comment to be unacceptable.

Being a computer engineer and a developer myself, I quite understand the need to comply to the most basic rules imposed by the OS. The code signing one has been introduce -years- ago and the compulsory sign is know since the first beta of ML: many months ago.

Regarding the other issue, Lightroom is the only application which keeps producing that log every time it starts, and I use a -lot- of software of any kind.

I really much prefer to speak with an Adobe employee to help each other fixing this issue, rather than keeping errors in one of the applications I use the most.
Photo of Paolo Avezzano

Paolo Avezzano

  • 58 Posts
  • 1 Reply Like
This error keeps showing, however, taken that some Apple app trigger the same message now and then, it matbe "normal" for heavy duty application.

This is definitely not a "byzantine rules" issue (as John Verne suggested) as Apple apps are obviously correctly signed :)