[black_eagle]

Excuse us simple folk for trying to intervene on your behalf. Of course, as the programmer you would also know best when to implement logging in the code.

What do you log though ? Every successful artist.nfo created followed by every album.nfo created ?  Or do you log failed writes, or artists/albums that have no info to export ?

Probably if I was going to log anything, it'd be the latter.  IE, no info to export for X.  However, one also has to consider that logging necessarily introduces more overheads and that as my export to separate files took over two hours to complete I'd probably not want to do it with debugging turned on.  If it could be moved to a background thread, then maybe it's something I'd consider, but I have no clue if that's either possible, desirable or of how much impact it may have on other areas of Kodi.  Certainly, if doing it in the background, one would have to block library updates, refreshes etc so it may well be more trouble than it's worth.

Also, my Kodi instances run for months at a time without restarting.  I generally have logging turned off completely for them as otherwise the logs just get ridiculously big (even without debug turned on).  Reproducing the issue with debug enabled may not even be possible, depending upon how/why it occurred in the first place.  However, if the OP is able to reproduce the issue then I'm sure Dave would do his utmost to help.

In a lot of cases (and I'm not suggesting for a second that this is the case here!), users mis-understand settings or expect a certain result and when that doesn't happen, blame the program they are using, irrespective of the fact (which most likely, they are not aware of) that they have configured something incorrectly.  I see this all the time in my 'day-job'.