Drive mapping resulted in 32GB Log file!

[grannysmith59]

I can't open the log file because it's 32.1 GB in size

I noticed because I received the attached error message

[grannysmith59]

CPU usage 98 to 100%

My new log since deleting the huge one is already 250 MB after 28 minutes!

It contains nothing but this over and over:

2021.02.17 14:13:00:9365 - DirectoryMonitory - File System Watcher Error! The parameter is incorrect
2021.02.17 14:13:00:9365 - Attempting to recreate the DirectoryMonitor
2021.02.17 14:13:00:9375 - DirectoryMonitory - File System Watcher Error! The parameter is incorrect
2021.02.17 14:13:00:9375 - Attempting to recreate the DirectoryMonitor
2021.02.17 14:13:00:9385 - DirectoryMonitory - File System Watcher Error! The parameter is incorrect
2021.02.17 14:13:00:9385 - Attempting to recreate the DirectoryMonitor
2021.02.17 14:13:00:9385 - DirectoryMonitory - File System Watcher Error! The parameter is incorrect
2021.02.17 14:13:00:9385 - Attempting to recreate the DirectoryMonitor
2021.02.17 14:13:00:9395 - DirectoryMonitory - File System Watcher Error! The parameter is incorrect
2021.02.17 14:13:00:9395 - Attempting to recreate the DirectoryMonitor
2021.02.17 14:13:00:9425 - DirectoryMonitory - File System Watcher Error! The parameter is incorrect
2021.02.17 14:13:00:9425 - Attempting to recreate the DirectoryMonitor
2021.02.17 14:13:00:9435 - DirectoryMonitory - File System Watcher Error! The parameter is incorrect
2021.02.17 14:13:00:9435 - DirectoryMonitory - File System Watcher Error! The parameter is incorrect
2021.02.17 14:13:00:9435 - Attempting to recreate the DirectoryMonitor
2021.02.17 14:13:00:9435 - Attempting to recreate the DirectoryMonitor
2021.02.17 14:13:00:9455 - DirectoryMonitory - File System Watcher Error! The parameter is incorrect
2021.02.17 14:13:00:9455 - Attempting to recreate the DirectoryMonitor
2021.02.17 14:13:00:9475 - DirectoryMonitory - File System Watcher Error! The parameter is incorrect
2021.02.17 14:13:00:9475 - Attempting to recreate the DirectoryMonitor
2021.02.17 14:13:00:9485 - DirectoryMonitory - File System Watcher Error! The parameter is incorrect
2021.02.17 14:13:00:9485 - Attempting to recreate the DirectoryMonitor

[grannysmith59]

It turns out that this was caused by mapping a drive letter to the "camera file path"

I have setup all of my cameras again (an edit button would be nice next to the add camera and remove camera buttons) and this time entered the full path and the log stopped growing exponentially!

I then setup a new camera using the mapped drive letter, and it started growing again.

[Ken98045]

Sorry for the very long delay. I didn't notice the issue in Github.

This was caused by repeatedly attempting to restart the folder watching processing. Every time it tried there was a log entry. Hence the very, very large log file. This will be fixed in versions greater than 3.1.1.

There was probably a related problem with using the drive mapped file path. I have been able to use a mapped drive letter for a network path for a long time with no problem, but was probably a bug related to this.

Note that you should not use a mapped drive to folder on a local PC due to performance issues (although it does/should work). I tried that with a large camera folder (40K files) and it took 30++ times longer to load the camera working set. I'm not quite sure why since this should be something Microsoft could optimize.