File handle not release without closing app

Nick

If I opened project A, without closing app and open another project B with the same instance of the editor, I could not delete the project A folder. Probably due to file handle not released.

Nick

Nate

I tried it but was able to delete project A. Can you please try a tool like Lock Hunter to verify Spine keeps a lock on the folder?

Nick

Did you try to delete the whole containing folder? The weird part is I can delete every single files inside the project folder. It is the folder that contain the project cannot be deleted until I close Spine. Note: the 2nd project I opened is outside of that 1st project folder so it should not cause problem. I can still reproduce it with both beta and non-beta build.

Nate

Yep, I created 2 spineboy project copies:
http://n4te.com/x/8632-Desktop.zip
I open a, then open b, with b still open I delete the whole a folder, deletes successfully. I even modified the projects so some images are in a subfolder, but it still works.

Spine uses Windows filesystem APIs to watch the images folder for changes. That's why you can't delete the images folder when a project is open. It closes down those watches when a project is unloaded though. Maybe for some reason your Windows doesn't release them.

Using a tool like Lock Hunter you can see which processes have a lock on a file or folder (and can remove the lock). It would be interesting to see if it really is Spine that has the lock. If so, are you doing any other steps other then opening project a, then b, then deleting the a folder?

In 4.0.63-beta you can use `

trace-files` and Spine will log when file watches are opened/closed.

We found Import Data can cause file watches to remain open. We'll have it fixed in 4.0.63-beta.