Closed JabRef processes remain running after "closing"

[hsvia]

Hi together,

when I close a 5.0-dev "Jabref program" the process itself remains running forever until I kill them explicitly. If another "Jabref program" is started, another process is added and so on. The processes are no longer visible or accessible for the user. Nevertheless, the JabRef installer detects them and forces me to kill them.
Below a screenshot of my process-explorer with 3 running processes while the desktop is empty.

Best, [Hartmut]

JabRef 5.0-dev--snapshot--2018-11-04--master--185c47a7a
Windows 8.1 6.3 amd64
Java 1.8.0_191

AND

JabRef 5.0-dev--snapshot--2018-11-04--master--185c47a7a
Windows 10 10.0 amd64
Java 1.8.0_191

[Siedlerchr]

Cannot confirm this on Windows 10 with the JabRef 5.0-dev--snapshot--2018-11-04--master--185c47a7a
After I exit JabRef it closes down, it actually needs a few seconds until it is shutdown.

The other issue is the same as #4023

[hsvia]

You are right, the 3 (and sometimes more) orphan jabrefs accumulated originate from version 4.31. I had started both programs intermixed and on win 8.1 and win 10 generated orphans. On win 8.1 and win 10 the jabref 5.0dev shuts down after some 10-20 seconds. No problem with 5.0dev.

JabRef 4.3.1
Windows 8.1 6.3 amd64
Java 1.8.0_191

[Siedlerchr]

Due to a lack of resources we are only able to support the latest version. There might be some bugs in older versions, which are already fixed. In this case we won't fix it on the JabRef 4.3.1 side. So only 5.x versions will shutdown flawlessly

[thenolfar]

I don't know if this is the right Issue,
but when I run JabRef4.3.1 on ubuntu from terminal with java -jar, after closing the window, the process does not terminate. So when I want to close the terminal, it complains that a process is still running.
I do not encounter data loss or any problems because of it, though.

[Siedlerchr]

@thenolfar Please use the latest development version from https://builds.jabref.org/master/ The bug is only fixed there.