Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Etcher.exe creates/runs batch script every 2 seconds indefinitely, at idle

See original GitHub issue

Version 1.0.0
Windows 10 64-bit
Burning images not necessary to recreate error
Nothing in DevTools that helps

My hard drive was filling up, so I did some analysis and found an obscene number of temp files in %UserProfile%\AppData\Local\Temp. They’re all the same exact file, but with a different random name, according to the convention: tmp-<pid><randomchar x12>.bat

Every 2 seconds, I see this Etcher process create a cmd process to run this batch script. It is the second of three subthreads of Etcher.exe, run with --renderer.

I haven’t looked too much into what the script does, but I found a copy of it uploaded to both Pastebin and VirusTotal.

Recreating the issue is as simple as just executing Etcher.exe and letting it run.

It has created over 1000 files in the time it took me to write this.

It should be noted that this doesn’t noticeably impact the performance of Etcher - I’ve created a few images in the last day or two. The only reason this came to my attention is because it was filling up my disk. At this rate, it consumes 354MB of disk daily. That’s less of a concern than the 43,200 files created daily. At about 100,000 files, Windows Explorer starts to choke when you try to browse a directory.

Again, this is a great piece of software - imaging stuff is so much easier. Just a bit alarmed to see this churning out more than just images 😉