JDK-8135224 : .oracle_jre_usage directory is created in user home directory
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc-agent
  • Affected Version: 8u60,9
  • Priority: P2
  • Status: Closed
  • Resolution: Not an Issue
  • OS: os_x
  • CPU: x86
  • Submitted: 2015-09-08
  • Updated: 2019-09-10
  • Resolved: 2018-11-15
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbd_minorResolved
Related Reports
Duplicate :  
Relates :  
Relates :  
Description
FULL PRODUCT VERSION :
java version "1.8.0_60"

ADDITIONAL OS VERSION INFORMATION :
Darwin 13.4.0 Darwin Kernel Version 13.4.0: Wed Mar 18 16:20:14 PDT 2015; root:xnu-2422.115.14~1/RELEASE_X86_64 x86_64

A DESCRIPTION OF THE PROBLEM :
Executing any java process creates .oracle_jre_usage directory in the users $HOME directory with a single timestamp file inside it. 

This started happening with the JDK 1.8u80 update (in previous versions such directory was not created). 

Note that this is not an appropriate location to store such files. In Mac OS X convention such files ought to be stored in 

~/Library/Application Support/Oracle/Java/

However, I am not sure if JRE usage tracking should be enabled by default to begin with.

REGRESSION.  Last worked in version 8u51

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Invoke java or javac and the ~/.oracle_jre_usage directory is (re-)created



REPRODUCIBILITY :
This bug can be reproduced always.


Comments
JDK-8198426 has removed this feature.
15-11-2018

As JDK-8134300 was a P2, I am setting this one to P2 as well.
02-11-2016

Should be core-svc as per JDK-8134300 - the changes are not in the hotspot code but in the JDK.
26-04-2016

Agree, this would be a runtime bug (previously serviceability)
26-04-2016

Curious as to why is this an install bug? The .oracle_jre_usage is not created by install team/code and this is most likely a VM issue..
26-04-2016

I'm re-opening this bug. JDK-8134300 fixed this for Windows only, but this should be fixed on all platforms, both OS X and Linux/Solaris.
22-04-2016

Confirmed this for MAC OS X as well. Closing this as duplicate of JDK-8134300
09-09-2015