JDK-8231288 : "jhsdb jmap" test needed to reproduce issues that used to be reproduced by JShellHeapDumpTest
- Type: Sub-task
- Component: hotspot
- Sub-Component: svc-agent
- Affected Version: 14
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2019-09-20
- Updated: 2019-10-09
- Resolved: 2019-10-03
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 14 |
|---|
14 b18Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
JShellHeapDumpTest seems to uncover a number of JMap bugs that seem to be related to the underlying java program mutating while trying to produce the hprof file. See the parent of this CR. However, after fixes for JDK-8228625 are done, you will no longer see these failures (or at best they will be very very rare) because the test will be allowing the jshell process to run until it reaches the user input prompt, thus the process will essentially be asleep, making for a safer state for JMap to work in. We need to add another test very similar to JShellHeapDumpTest, but without the 2 second delay, so these problems reproduce again. The test will need to be immediately problem listed because it will cause too many failures.
Comments
|