Details
-
Type: Bug
-
Status: Closed
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 2.11.1.1, 2.11.1.2, 2.11.1.3, 2.11.1.4, 2.11.1.5, 2.11.1.6, 2.11.2.0
-
Component/s: file format issue
-
Labels:None
-
Environment:Windows 10, certain circumstances, not all users
-
Urgency:Not urgent
Description
When Jalview saves a file it produces the below exception with a '"issue with backup file. Continue anyway?" or somesuch dialog'
[ probably: label.backupfiles_confirm_save_file_backupfiles_roll_wrong + label.backupfiles_confirm_save_new_saved_file_not_ok + label.continue_operation found in BackupFiles.rollBackupsAndRenameTempFile() ]
When saving again straight away the save succeeds.
In the reported case, the file is on a non-main letter drive (E:) and the error happens when the application is installed on either C: or E: drive, although it is not clear if this is necessarily connected. The different drive is an internal HDD not network.
This happens consistently (for the user) whether Backupfiles is enabled or disabled.
See comment https://issues.jalview.org/browse/JAL-3628?focusedCommentId=23910&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-23910
The exception is (full DEBUG in attachments)
java.nio.file.FileSystemException: E:\PATH.fa: The process cannot access the file because it is being used by another process.
at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86)
at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)
at sun.nio.fs.WindowsFileCopy.move(WindowsFileCopy.java:376)
at sun.nio.fs.WindowsFileSystemProvider.move(WindowsFileSystemProvider.java:287)
at java.nio.file.Files.move(Files.java:1395)
at jalview.io.BackupFiles.moveFileToFile(BackupFiles.java:908)
[ probably: label.backupfiles_confirm_save_file_backupfiles_roll_wrong + label.backupfiles_confirm_save_new_saved_file_not_ok + label.continue_operation found in BackupFiles.rollBackupsAndRenameTempFile() ]
When saving again straight away the save succeeds.
In the reported case, the file is on a non-main letter drive (E:) and the error happens when the application is installed on either C: or E: drive, although it is not clear if this is necessarily connected. The different drive is an internal HDD not network.
This happens consistently (for the user) whether Backupfiles is enabled or disabled.
See comment https://issues.jalview.org/browse/JAL-3628?focusedCommentId=23910&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-23910
The exception is (full DEBUG in attachments)
java.nio.file.FileSystemException: E:\PATH.fa: The process cannot access the file because it is being used by another process.
at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86)
at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)
at sun.nio.fs.WindowsFileCopy.move(WindowsFileCopy.java:376)
at sun.nio.fs.WindowsFileSystemProvider.move(WindowsFileSystemProvider.java:287)
at java.nio.file.Files.move(Files.java:1395)
at jalview.io.BackupFiles.moveFileToFile(BackupFiles.java:908)
Attachments
Issue Links
- blocks
-
JAL-3628 Unable to save update to an existing file on Windows due to 'something went wrong with the backups of this file' dialog when backups are disabled
- Closed
-
JAL-3939 Revisit and refactor AlignFile/FileParse input stream close/dispose semantics
- Open
- related with
-
JAL-3935 (Windows only) Jalview inconsistent in releasing file handle upon file close
- Closed