Temporary files not deleted on exit about flexdll HOT 3 CLOSED

It turns out it's been doing this for a while! If flexlink is passed a C file on the command line (e.g. the primitives file in -custom mode) then it compiles a temporary object which is marked for deletion on exit. The problem is that flexlink doesn't close objects/libraries which it's read symbols from because it used to have infrastructure where sections were read lazily.

from flexdll.

I'm fairly sure that switching winpthreads to static in 5.0 is going to require a tweak in flexlink - I'm expecting to get to that when I get back from holiday in a few weeks. Would it be OK for a release of flexlink to wait until that's cleared up? I'm guessing in the meantime that clearing out the tmp directory on the Windows workers has bought a little more time?

from flexdll.

Thanks for the quick fix! Yes, the release can wait for several months. I estimate it takes about one year for our CI Windows machine to slow down noticeably because of the overfull /tmp directory.

from flexdll.