P: Human readable diagnostic logging

Forum|Forum|19 hours ago
July 10, 2026
1 reply
11 views

Add High level logging, with timestamps, to a text file to record key events such as -
Launched LrC version xxx
Log core elements from System Info
Opening Catalog X:\parh\name.lrdata
Detecting GPU, Initialising GPU, GPU Driver version, GPU settings
Major catalog activities - compressing, checking,
Edit in application (log the app, the filename)
Import/Sync summary
ALL failures and warnings
User launching/pausing backgroud tasks
User switching between modes (Library, Develop, Map etc)
If possible - Last activity before application becomes unresponsive.
Memory limitations
I am sure there are many more.

I appreciate it is difficult to find a balance between too much and too little.

Maybe record the number of times that certain faults re-occur.
If possible, use this count to increase logging levels of certain components so that future logs can concentrate on the issue.

And then :
Rolling logs, so keep the last N logs, or last X days of logs.
Tool to view any log.
Cut-n-paste to sent to AI tool to review. or copy to clipboard.

johnrellis

Legend

Since I do a large amount of troubleshooting, here and with users of my plugins, I’d greatly appreciate improved logging.

I’d settle simply for logging the details of every error in “lrc_console.log”. Too often, some low-level error gets propagated upwards to the higher levels of LR and displayed to the user with a misleading or vague error message (or none at all), e.g. “Unknown error”. Simply having a policy of always logging unexpected low-level exceptions would greatly help those of us who troubleshoot.

Also, on Mac, “lrc_console.log” records the Lua call stack of errors that occur in the Lua-coded parts of the application. Not only does that help plugin developors immensely, it also helps generic troubleshooting, since it can often indicate the locus of the problem.

But on Windows, the Lua errors and call stacks aren’t recorded, a gratuitous omission.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.