JabRef version <4.3.1> on < Windows 10>
<Closing the jabref not only the memory is not released but in the task manager the jabref seems to be running. Even after half an hour. 4 "instances" occupy more than 1 GB. Only manual kill the otherwise not running task releases the memory. If you are doing the same with the development version running directly the jar file, javaw remains in the memory and reserves/uses that. This latter is not always reproducible. Using multiple libraries only the occupied memory increaesed not the repeated appearance of jabref.
Using the direct running of jar file (431) only Javaplatform binary.../javaw is seen (taskmanager/sysinternals process explorer)>
Steps to reproduce the behavior:
- ...open jabref with or without a bib file
- ...close it
- ...repeat it a couple of times, in different time and the memory occupancy is accumulated.
Log File
Paste an excerpt of your log file here
JabRef version <4.3.1> on < Windows 10>
<Closing the jabref not only the memory is not released but in the task manager the jabref seems to be running. Even after half an hour. 4 "instances" occupy more than 1 GB. Only manual kill the otherwise not running task releases the memory. If you are doing the same with the development version running directly the jar file, javaw remains in the memory and reserves/uses that. This latter is not always reproducible. Using multiple libraries only the occupied memory increaesed not the repeated appearance of jabref.
Using the direct running of jar file (431) only Javaplatform binary.../javaw is seen (taskmanager/sysinternals process explorer)>
Steps to reproduce the behavior:
Log File