JDK-8255973 : Add more logging to debug JDK-8255917
- Type: Sub-task
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 16
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-11-06
- Updated: 2020-11-19
- Resolved: 2020-11-13
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 16 |
|---|
16 b25Fixed  |
Related Reports
|
Relates :
|
Description
There's very little information in the test log to see what happened. Since this bug is not easily reproduced, we should add more logging in the test to diagnose the failures. [1] -Xlog:metaspace*=debug should be added to test/hotspot/jtreg/runtime/cds/SharedBaseAddress.java [2] virtualMemoryTracker.cpp should use Unified Logging to log the changes in _reserved_regions.
Comments
|