Potential bug in os::split_reserved_memory on windows

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: P4
    • 17
    • Affects Version/s: 16
    • Component/s: hotspot
    • None

      The code looks like this on windows:
        release_memory(base, size);
        attempt_reserve_memory_at(split, base);
        attempt_reserve_memory_at(size - split, split_address);

      After the release and before the re-reservations, another thread could reserve that memory. Investigate the effects of this.

      We've had similar bugs in the past, where memory are temporarily unmapped and non-JVM threads reserves memory in the requested area.

            Assignee:
            Yumin Qi
            Reporter:
            Stefan Karlsson
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: