debug.log became 100+gigs overnight

[p0l1c3c4r]

Describe the bug
DupeGuru created a log file over 100 Gbs big in the folder C:\Users<USER>\AppData\Roaming\Hardcoded Software\dupeGuru overnight.
I have no idea what caused this, I was using the software to remove duplicates on different drives than the system drive, I ran the software on 2 TB of data several times, it was working perfectly, but suddenly the log file became 100+ gigs. It was really hard to locate, because somehow spacesniffer could not find it for several runs, it was stuck at 25% multiple times, but I'm not sure it's related, it was a bad sector or something.

To Reproduce
Steps to reproduce the behavior:

1. Use DupeGuru
2. .....
3. ......
4. Log file is over 100 gigs (sorry)

Expected behavior
Log file is not set to debug by default?

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Version [e.g. 4.3.1]

Additional context
None