- changed status to invalid
Apogy does not cleanup after OreKit
Issue #127
resolved
Each time Apogy is launched, OreKit create a different folder oreKit<UID> in /tmp. This folder is quite large (~6MB).
These folders are never cleaned up; it ends up consuming a lot of disk space.
Example:
#!
$ du -sh /tmp/oreKit*
5.9M /tmp/oreKit1183804986942103006
5.9M /tmp/oreKit1315161983479630046
5.9M /tmp/oreKit1617216492147869518
5.9M /tmp/oreKit1999830849357715061
5.9M /tmp/oreKit2259121590240176996
5.9M /tmp/oreKit2641148442235822119
5.9M /tmp/oreKit3306472269140599578
5.9M /tmp/oreKit3437677608156381173
5.9M /tmp/oreKit3865055337747552759
5.9M /tmp/oreKit39856270501272063
5.9M /tmp/oreKit416661882364343756
5.9M /tmp/oreKit533961051959082516
5.9M /tmp/oreKit5700968023732700111
5.9M /tmp/oreKit7626670288762977621
5.9M /tmp/oreKit8054556916348146764
Comments (3)
-
-
- changed status to open
Reproduced on a different platform. We'll investigate.
-
- changed status to resolved
Fixed in apogy.ots we'll be available in the next Apogy develop/latest build.
- Log in to comment
The default behaviour is these files are automatically deleted once the application (Eclipse product) gets completed. If the JVM crashes, it is possible some temporary files/directories are not deleted. Delete manually the /tmp/ore* directories and see if the problem still occur. We are unable to reproduce the problem.