[Windows] - Running a project with sdk when a session already exists will not delete the older session

[TheAmg]

Describe the bug

On starting a process with the sdk through docker on windows for the 2nd time will cause a few issues.

• The older session will not be deleted.
• DirectInvoke will work, but no candidates will be seen.

To recreate -

• Start an application with sdk on windows through docker.

• Stop process and DO NOT delete sessions manually.

• Start the process again/start another process. New candidates from your current session will not show up.

• This can be observed easily in the frequency logging UI test in the test branch on UI testrun.

Reproduction steps

1. Start unlogged-spring-maven-demo on windows with docker (ui-test-clean)
2. Stop process, don't delete sessions. Remove containers, images and volumes.
3. Start the process through docker again, no new candidates show up.
   ...

Alternative

1. Run UI tests on Windows

Expected behavior

For the older session to be deleted and candidates from only the current session to be seen.

Additional context

No response

[kartikeytewari-ul]

The old session's selogger files are deleted correctly, but the execution.db file is not deleted. When ide is open, and a manual attempt is made to delete the execution.db, windows come up with error message, that the file cannot be deleted because it is used by another binary process.

This seems to happen because plugin still have a lock on it, thus windows is unable to delete it.