Building a dev module version causes persistent high CPU usage

[arikorn]

When a Companion auto-restarts to load a module with changed files, Companion CPU usage goes up to 70% while idle (on my Windows system, even without the admin WebUI open) and stays there. See images below. I did this by just running yarn build in my Typescript projects without changing the file contents.

This behavior appears to be the same in Companion version v4.0.3, v4.1.0, and the latest 4.2 beta: 8448, with module-base versions 1.11.0 - 1.13 (only 1.11 was tested with 4.0.3). I didn't check earlier versions.

I have been able to reproduce the problem with module-template-ts, but only inconsistently (maybe one in 10 null re-builds?). The problem shows up much less consistently, for example, the Osee GoStream module. It does it for me even if the module is disabled. (It's possible that having buttons that use the module is necessary for the problem to show up.)

OS: Windows 10
Browser: Chrome (though the browser doesn't have to be open.)

Normal usage:

After re-building the module:

[arikorn]

FWIW, I've profiled the modules under these conditions and they're all idle. I've tried to debug from a core dev, but can't find a way to debug the launcher in WSL with dev modules: with v4.1.0 new "advanced settings" window appears but with no content; with older builds I can set it all up, and it "acknowledges" the dev modules in the console output but it doesn't appear to be tracking file changes, nor can I launch the GUI from it... Anyway, I'm hoping you can reproduce my problem!!!