Allow unloading of dynamic Proxy implementation classes

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Unresolved
    • Priority: P4
    • tbd
    • Affects Version/s: 24
    • Component/s: core-libs
    • None

      Dynamic proxy implementation classes are currently strong. With dynamic proxy converted to hidden classes, they can no longer be statically discovered by user code via `Class.forName` and their unloading will have no observable effect. This allows us to garbage collect unused Proxy classes to save some memory.

      This requires specification changes to dynamic Proxy, as currently it specifies that Proxy classes are defined only once to the given class loader, which will no longer be true.

            Assignee:
            Unassigned
            Reporter:
            Chen Liang
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: