JDK-7012519 : JDK7 Built with on Windows with VS2010, will not be shipping msvcrt.dll, just msvcr100.dll
  • Type: Bug
  • Component: tools
  • Sub-Component: visualvm
  • Affected Version: 7
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2011-01-14
  • Updated: 2024-04-12
  • Resolved: 2017-10-17
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
tbdFixed
Related Reports
Relates :  
Description
JDK7 has been changed to use VS2010 on Windows XP/2003 now and the dll/exe files built by the jdk7 makefiles now only depend on msvcr100.dll and no longer on msvcrt.dll (on 32bit or 64bit).
Previously, even when built with VS2003 the dependence on msvcrt.dll was very limited, mostly being dependent on msvcr71.dll.

The issue at hand is that the old runtime msvcrt.dll will no longer be shipped with jdk7, and doing an inspection of all the dll and exe files in the jdk7 shipment (using dumpbin /dependents), only the visualvm exe/dll files had a dependence on msvcrt.dll.

Once jdk7 stops shipping msvcrt.dll I assume any use of it will likely find one somewhere else, either in the system32 directory or somewhere in the PATH (although that may be arbitrary). The concern may be that you won't know which version you got.

Ideally, we would like to see the visualvm binaries built with the same compiler as the jdk7 product, but in any case I felt it was important to file this bug as a heads up to the visualvm team.
See 6950375 for more info.

Comments
Fixed in latest JDK 8 builds bundling VisualVM.
17-10-2017