Why is there a debug file on my computer and how to I fix it

I've seen these files on two PCs of mine that don't have VSCode. And several times when I tried to delete the file, it says that Edge has the file locked, so it definitely seems browser-originated.

[1011/110838.410:ERROR:directory_reader_win.cc(43)] FindFirstFile: Le chemin d’accès spécifié est introuvable. (0x3)

I am amazed that so many people have the same problem and that so many "specialists" are not the slightest beginning of a solution!

Everyone sleeps at Micosoft ??

Does anyone hitting the issue have Visual Studio code installed?

I do, but as discussed at https://answers.microsoft.com/en-us/windows/forum/all/vs-code-creating-debuglog-file-all-the-time/0b7640b2-7a22-40ad-b137-d255c90d43a4 the debug.log files appear even when I haven't used VSCode that day, and in other locations such as the Desktop.  

I can't exclude the possibility that VSCode is involved, but the connection may just be that the Git integration just highlights the debug.log files.  That is how I first noticed, but now I've seen them in other locations.

Yes, i can confirm that using Edge probably generates the debug.log,

i have found it in 2 computers, at home and the office, both windows 10.

All the browsers I've seen mentioned in any of these threads -- there are many in the last week or so, just search for the exact "FindFirstFile" error message and you'll find a bunch -- are based on Chromium, the open-source engine that powers Chrome.  Brave, Chrome, the new MS Edge, your Opera, all of them are built on top of Chromium.  That strongly suggests that a bug was recently introduced to Chromium that's causing this.