[TIKA-1738] ForkClient does not always delete temporary bootstrap jar

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Fix Version/s: 1.17, 2.0.0-BETA, 2.1.0
• Component/s: core

Environment

Windows 10

• Flags: Patch
• Assignee: Unassigned
• Reporter: Yaniv Kunda
• Created: 20/Sep/15 12:10
• Updated: 17/Aug/21 13:30

Description

ForkClient creates a new temporary bootstrap jar each time it's instantiated, and tries to delete it in the close() method, after destroying the process.
Possibly a Windows-specific behavior, the OS seem to still hold a handle to the file a bit after the process is destroyed, causing the delete() method to do nothing.
This is recreated by simply running ForkParserTest on my machine.

In a long-running process,this could fill the temp folder with many bootstrap jars that will never be deleted.