Lightroom: Change in Lock File behaviour?

  • 2
  • Problem
  • Updated 4 years ago
It used to be that attempting to start Lightroom when a lock file was already present alongside the catalog file (e.g. after a system crash or power failure) would fail. The lock file would need to be deleted before Lightroom could be restarted, right?

Maybe not. Due to a faulty laptop (frequent freeze requiring force power off) I've recently noticed that Lightroom will in fact happily restart even though the lock file from the previous session is still present. So is this a bug, or has the lock file behaviour been changed by design?

Laptop is running 3.4.1 on Win7 32bit, but Beat has also confirmed the same behaviour on 3.3. Further specifics (including screenshots) available if needed.
Photo of Jim Wilde

Jim Wilde

  • 136 Posts
  • 26 Reply Likes

Posted 7 years ago

  • 2
Photo of Beat Gossweiler

Beat Gossweiler

  • 238 Posts
  • 38 Reply Likes
Funny enough, I'm not even able to reproduce what I (think) was normal behaviour (no start with lock file present) under LR 2.7. Might it be a O/S difference (XP vs. Win7)?

Beat
Photo of Jim Wilde

Jim Wilde

  • 136 Posts
  • 26 Reply Likes
I think you might be right, Beat....I've just tested with LR1.4 with the same result, i.e. no restart problem with a pre-existing lock file present.
Photo of jdv

jdv, Champion

  • 728 Posts
  • 56 Reply Likes
I don't know about the Lightroom implementation, but in SQLite, the mere existence of a lockfile is not immediately an indication of a problem on startup. Between that and the journal file the DB can usually determine if the lockfile is actually protecting something. In those cases, the lockfile is rewritten w/o error.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 385 Reply Likes
Contents of lock file:

C:\Program Files\Adobe\Adobe Photoshop Lightroom 5.6\lightroom.exe
16476

i.e. two lines:
1. path to app which has catalog open.
2. ID of corresponding process.

Thus there is enough info for some intelligence.

(e.g. if no such process exists, then Lr knows it's not really locked by said app, and will just go ahead and open it, replacing the contents of the lock file)

~R.