Had this issue as well and was also running through VSCode like @rachel-piotraschke-organist. It may be something VS Code injects for debugging.