[Bug Report]: Opening menuconfig sometimes prevents building/flashing (VSC-465) #199
Labels
bug-report
Bug Report from users on Github (don't use this tag manually, its supposed to be used via the issue)
Describe the bug
This bug has been previously reported on the ESP-IDF forum, but noone actually discovered the root cause afaik: https://www.esp32.com/viewtopic.php?p=57477
I hate to say this, but it's not 100% consistent and I do not know why - sometimes these multiple ninja processes don't have any issues coinciding with each other, sometimes they do.
After opening menuconfig, a
ninja.exe
process probably sometimes leaves a file descriptor open, essentially blocking any new ninja process from accessing some files - logs don't say the exact path, but I assumebuild/.ninja_deps
.The fastest way to fix this is closing the workspace and opening it again - restarting VSCode also works, but is slower.
It does not happen without opening menucofig - I always dread opening it since discovering this, and it never happened without it.
In Task Manager, the process is sometimes a child process of Visual Studio Code
.
but sometimes not, and is just floating around with the other processes
Killing that process manually renders the menuconfig irresposive (any changes are not actually propagated to the
sdkconfig
file), even after closing and opening it again. Log:Output from console:
Output from menuconfig:
To Reproduce
To simulate the screenshots and logs in this issue, I essentially just kept opening & closing menuconfig, sometimes changing a value, and re-running
idf.py build flash -b 2000000 monitor
every time to see if anything changes.As I can't exactly state how this issue happens here is a video of this issue: https://youtu.be/rqNc46yaycY
Environment
The text was updated successfully, but these errors were encountered: