Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8156498

more places in the invoke.c that need protection with the invokerLock

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Not an Issue
    • Icon: P4 P4
    • tbd
    • 9
    • core-svc
    • None
    • generic
    • generic

      This is a fragment from my review of the fix:
        8153711: [REDO] JDWP: Memory Leak: GlobalRefs never deleted when processing invokeMethod command

      It seems, there are more places where an invokerLock critical section is missed.
      The following functions:
        - invokeConstructor
        - invokeStatic
        - invokeNonvirtual
        - invokeVirtual
        - saveGlobalRef

      These functions are called from the invoker_doInvoke() that we already had a problem with.

            cjplummer Chris Plummer
            sspitsyn Serguei Spitsyn
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: