Is it possible PhotoMechanic release 4.5.1.1 was compiled with some kind of debugging switch left 'on'? PM.log grows very large on my notebook computer.
Background information:
-----------------------
On my notebook computer (running on Win XP SP2), disk space is scarce and because of multiple projects, disk fragmentation has my constant attention.
After a recent defragmentation operation, I discovered a file that could not be defragmented and to my surprise it belonged to PhotoMechanic. The file in question is PM.LOG, on my notebook almost 800MB large and split in more than 40.000 fragments.
From a system management viewpoint, this was is completely unacceptable, both in terms of space and defragmentation. So I had to take drastic action: to move the file from my notebook to a quarantaine location on my main server, and delete the file on my notebook.
PhotoMechanic (version 4.5.1.1) seems to be running smoothly after this action. However, after opening and reading a folder with 15 RAW files and closing PhotoMechanic, PM.log was back, containing 330 lines of information. That 'fresh' PM.log is enclosed as an attachment to this post.
I would like to know when and why PhotoMechanic writes to PM.log and whether I can expect it to grow large and fragmented again.
[attachment deleted by admin]
