JDK-7152274 : msvcr100.dll should be treated like any other file during PIP
- Type: Bug
- Component: install
- Sub-Component: install
- Affected Version: 6u32,7u4,7u5
- Priority: P2
- Status: Closed
- Resolution: Fixed
- OS: generic,windows
- CPU: generic
- Submitted: 2012-03-08
- Updated: 2013-09-12
- Resolved: 2012-04-06
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.
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 | JDK 8 |
|---|---|---|
6u32 b04Fixed  |
7u4Fixed |
8Fixed |
Related Reports
|
Duplicate :
|
Description
Our JRE image has two copies of msvcr100.dll. To save on download size, we ignore this file during the building of the RtPatch binary diff file. We also duplicate the file during install. The deploy group has been moving/renaming directories a lot lately. When the directory has msvcr100.dll in it, it is causing problems (because it is ignored by rtpatch). We are only saving 313KB (compressed) for each copy of msvcr100.dll that we duplicate during install runtime. However, it is more robust and easier to maintain if we just take the 313KB hit on the download size and just treat this file like any other. There is a good chance that the deploy group may move directories with msvcr100.dll in the future.
Comments
|