Performance: jweak references not suitable for robust cache architecture

XMLWordPrintable

    • Type: Bug
    • Resolution: Rejected
    • Priority: P4
    • tbd
    • Affects Version/s: 9
    • Component/s: hotspot
    • None
    • gc

      Performance: jweak references not suitable for robust cache architecture

      #1 Contrary to the expectations, jweak objects that are destroyed with DeleteWeakGlobalRef() take more GC time than alive one, but with dead objects (see attached test case)

      #2 DeleteWeakGlobalRef() does not actually free the memory

      #3 jweaks are processed single threaded by the GC

        1. Test.java
          2 kB
        2. Test.java
          2 kB
        3. Test.c
          0.9 kB

            Assignee:
            Unassigned
            Reporter:
            Gerard Ziemski (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: