6 Replies Latest reply: Apr 11, 2012 1:55 PM by johnrellis RSS

    DEBUG code in LR 4.0

    gp7024 Community Member

      My windows installation of LR4 is generating a LrCatalog.log file containg DEBUG messages.

      Indicates to me there is some left-over debug code in the executable.

      It might run faster without this.

      Sample of file

      04/08/2012 11:14:28 DEBUG removing item about to be processed from queue: "Add c40-8927_8_9.tif to catalog"

      04/08/2012 11:14:28 DEBUG executing "Add c40-8927_8_9.tif to catalog"

      04/08/2012 11:23:55 DEBUG immediate execution of "Add c40-8924_5_6.tif to catalog"

      04/08/2012 11:23:55 DEBUG removing item about to be processed from queue: "Add c40-8924_5_6.tif to catalog"

      04/08/2012 11:23:55 DEBUG executing "Add c40-8924_5_6.tif to catalog"

      04/08/2012 12:00:10 DEBUG immediate execution of "Add c41-5206_7_8.tif to catalog"

      04/08/2012 12:00:10 DEBUG removing item about to be processed from queue: "Add c41-5206_7_8.tif to catalog"

      04/08/2012 12:00:10 DEBUG executing "Add c41-5206_7_8.tif to catalog"

      04/08/2012 14:34:52 DEBUG initializing writeAccessQueue

      04/08/2012 14:34:52 DEBUG immediate execution of "Add c41-4625_6_7.tif to catalog"

      04/08/2012 14:34:52 DEBUG removing item about to be processed from queue: "Add c41-4625_6_7.tif to catalog"

      04/08/2012 14:34:52 DEBUG executing "Add c41-4625_6_7.tif to catalog"

        • 1. Re: DEBUG code in LR 4.0
          johnrellis CommunityMVP

          Interesting.  Which plugins, if any, do you have installed?  If you temporarily disable the plugins and restart LR, is the log file still generated?  See this post:

           

          http://forums.adobe.com/thread/976387?tstart=0

           

          Also, where is the file being generated?

          • 2. Re: DEBUG code in LR 4.0
            Lee Jay Community Member

            Check your C:\Users\<user name>\AppData\Roaming\Adobe\Lightroom folder for a file called "config.lua".  If it's there, rename it or delete it.

            • 3. Re: DEBUG code in LR 4.0
              gp7024 Community Member

              Lee Jay: checked to not have that file.

              John R Ellis:  I have the Photomatix Pro export plugin v1.3 enabled and yes the files referenced are instances where I have used the plugin.

              So looks like that is the source.

              Will report this to HDRSoft.

              Thank you guys.

              • 4. Re: DEBUG code in LR 4.0
                johnrellis CommunityMVP

                Another user just reported this as well:

                 

                http://forums.adobe.com/message/4326750

                 

                He gave details of where the LrCatalog.log file was located (c:\users\<user>\documents), and with that I could see that I have one too and quickly figure out what's probably going on:

                 

                - The logging appears to be initiated by LR itself, not by plugins. It occurred without the presence of a "config.lua" file.

                 

                - The logging appears to come from the LR SDK's LrCatalog module, which provides plugins with access to the catalog. For example, these two lines:

                 

                03/17/2012 09:50:23 DEBUG initializing writeAccessQueue

                03/17/2012 09:50:23 DEBUG immediate execution of "Tag: apply keywords"

                 

                correspond to the Any Tag plugin invoking catalog:withWriteAccessDo ("Tag: apply keywords", function).  My log file had entries from other plugins that accessed the same SDK method.

                 

                - The logging may be disabled in LR 4.1RC.  The last entry in my LrCatalog.log file occurred just before I upgraded from LR 4.0 to LR 4.1RC.

                • 5. Re: DEBUG code in LR 4.0
                  **Guschtl**

                  Hi John, I investigated a bit in this issue.

                   

                  The" LrCatalog.log" is only generated when I enable either the MetadataWrangler or LRMogrify-Plugin (or both) and I hit the export button. The file is generated the moment the export dialog window appears (and any of the mentioned plugins are enabled). If both plug-ins are disabled and I press "export", no log is generated.

                   

                  As I said in my thread, I encounter no problems except the log-file.

                   

                   

                  my config:

                  LR4.0

                  newest versions of the MetadataWrangler and LRMogrify

                  Win7 32Bit Ultimate (German)

                  • 6. Re: DEBUG code in LR 4.0
                    johnrellis CommunityMVP

                    The" LrCatalog.log" is only generated when I enable either the MetadataWrangler or LRMogrify-Plugin (or both) and I hit the export button.

                    Yes, that seems consistent with my hypothesis about what's going on: LR 4.0 has some logging enabled for the Software Development Kit module that let's plugins manipulate the catalog.  That logging will only appear when the plugins actually call into the SDK to modify the catalog (directly or indirectly).  This is out of the control of the plugins themselves.

                     

                    It appears that LR 4.1RC has fixed this (at least on my computer).