Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 2.11.1.0, 2.11.2.0
-
Component/s: Dev and Dep, Jalview Project
-
Labels:
-
Environment:Win10
Description
This has been a problem for quite some time. It's peculiar to Windows since posix-based OS don't lock files if another program opens them.
In any case, sometimes Jalview opens files in Windows such that it locks the file. Sometimes it does not. This is a royal pita if I'm trying to e.g. update the file in a second program (or ftp over a new version or whatever). The only workaround is to constantly close the Jalview program.
Based on the behavior, I'm guessing that Jalview is having some sort of error upon opening a file and the handle gets left open, leaving the file locked by the OS. I can have a session where this never happens, but once it starts, I have to reboot the computer to get Jalview to behave (and it may or may not).
Sorry I can't give more information; I'm guessing it'll be annoying to track down.
In any case, sometimes Jalview opens files in Windows such that it locks the file. Sometimes it does not. This is a royal pita if I'm trying to e.g. update the file in a second program (or ftp over a new version or whatever). The only workaround is to constantly close the Jalview program.
Based on the behavior, I'm guessing that Jalview is having some sort of error upon opening a file and the handle gets left open, leaving the file locked by the OS. I can have a session where this never happens, but once it starts, I have to reboot the computer to get Jalview to behave (and it may or may not).
Sorry I can't give more information; I'm guessing it'll be annoying to track down.
