bug: Dozens of instances of f951 running when using autosave afterdelay

[jordan4ibanez]

Is there an existing issue for this?

• I have searched the existing issues

I have tried the Pre-Release of the extension.

• I have replicated the Issue in the latest Pre-Release

Description

I am working on a fairly large project. When I start working on the main cross over file of all my modules, my operating system literally gets halted to a crawl due to process f951 being spawned over and over. I am just using this extension with defaults.

I wouldn't mind this, but I just saw this thing absolutely demolish my laptop's battery from 59% to 34% in 15 minutes.

Screenshots

Expected Behaviour

Limit the number of instances of f951 this thing can spawn.

Version of Modern Fortran

v3.4.2024101621

Version of Visual Studio Code

1.95.3

Platform and Architecture

Endeavour OS x86_64

Additional Information

Ryzen 5500u, 32GB ram.

This also slows down my desktop with a 9700x and 48 GB of ram as well at some points, so this is definitely not only an issue with this being run on a laptop.

[machsix]

I have the same issue with ifort as the compiler. Dozens of intel64/fortcom instances. and they seem to compile the same file

Edit:
the fortcom process doesn't close when the file is closed.
and a new fortcom process is open every time when the file is opened.

Edit2:
After running the "fortcom" process out of vscode, I found the program hangs. Later found out it's because an include path was set incorrectly and the linter ifort never exits