Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upon exiting Jabref is still active in the Windows task manager #4403

Closed
bernhard-kleine opened this issue Oct 23, 2018 · 3 comments
Closed

Comments

@bernhard-kleine
Copy link

JabRef 5.0-dev--snapshot--2018-10-23--master--eda8e2628
Windows 7 6.1 amd64
Java 1.8.0_181

Steps to reproduce:

  1. Open the last development version
  2. Check in the task manager that is present
  3. Exit JabRef
  4. 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.

@bernhard-kleine 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
@Siedlerchr
Copy link
Member

Do you have autosave enabled? #4352

@bernhard-kleine
Copy link
Author

bernhard-kleine commented Oct 24, 2018

Yes I do. However, unchecking did not change the behaviour.

@Siedlerchr
Copy link
Member

Closing this issue as duplicate of #4321

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants