JDK-6647268 : memory leak during install
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 6u10
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2008-01-04
  • Updated: 2010-09-17
  • Resolved: 2008-06-16
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.
JDK 6 JDK 7
6u10 b12Fixed 7Fixed
Related Reports
Relates :  
JDK-6647280 - no logfile for zipper.exe and unpack200.exe during JRE install
Description
There is a memory leak with CreateLogFile() and MSIGetLogFileName()
char* CreateLogFile() in deploy\src\plugin\win32\regutils\RegCommon.cpp
allocates char *absTempFileName = new char[MAX_PATH]
and returns absTempFileName but MSIGetLogFileName() does not free the memory.
I assume the memory is freed when the install exits.
Comments
SUGGESTED FIX in webrev for 6647280 functions rewritten so calls to CreateLogFile() pass in a max size / pointer to the string and the memory is allocated on the stack.
01-02-2008
SUGGESTED FIX in webrev for 6647280
30-01-2008
EVALUATION char* CreateLogFile() in deploy\src\plugin\win32\regutils\RegCommon.cpp allocates char *absTempFileName = new char[MAX_PATH] and returns absTempFileName but MSIGetLogFileName() does not free the memory.
04-01-2008