To analyze JDK-8256729 further, we need more tracing:
1)We should print a mapping of the split area if os::split_reserved_memory fails
2)The print-mapping code on windows has some shortcomings:
- does not handle huge areas well (it should be possible to print the whole address space, similar to proc/pid/maps on Linux)
- Protection information is printed wrong
- can be printed more concise and maybe adorned with some basic range info, e.g. library mappings
1)We should print a mapping of the split area if os::split_reserved_memory fails
2)The print-mapping code on windows has some shortcomings:
- does not handle huge areas well (it should be possible to print the whole address space, similar to proc/pid/maps on Linux)
- Protection information is printed wrong
- can be printed more concise and maybe adorned with some basic range info, e.g. library mappings
- duplicates
-
JDK-8256819 [windows] os::print_memory_mappings() should avoid probing out-of-range address areas
-
- Closed
-
- relates to
-
JDK-8255917 runtime/cds/SharedBaseAddress.java failed "assert(reserved_rgn != 0LL) failed: No reserved region"
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
(2 links to)