You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The jabref entry remains open in the task manager.
BTW the backup file .sav is not deleted upon closing the database.
This problem is not new. It causes upon opening e.g. message/question whether to use the backup version of a database or not, since the .sav file is not deleted when closing. In my humble opinion, the underlying problem is partially responsible for fact that while the port 65?? is checked in options, there are two different JabRef entries possible with JabRef 5.0dev. There is something fishy with the Windows interaction.
The text was updated successfully, but these errors were encountered:
bernhard-kleine
changed the title
Upon exit Jabref is still active in the Windows task manager
Upon exiting Jabref is still active in the Windows task manager
Oct 23, 2018
JabRef 5.0-dev--snapshot--2018-10-23--master--eda8e2628
Windows 7 6.1 amd64
Java 1.8.0_181
Steps to reproduce:
BTW the backup file .sav is not deleted upon closing the database.
This problem is not new. It causes upon opening e.g. message/question whether to use the backup version of a database or not, since the .sav file is not deleted when closing. In my humble opinion, the underlying problem is partially responsible for fact that while the port 65?? is checked in options, there are two different JabRef entries possible with JabRef 5.0dev. There is something fishy with the Windows interaction.
The text was updated successfully, but these errors were encountered: