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

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

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Open
    • Priority: P4
    • Resolution: Unresolved
    • Affects Version/s: 9
    • Fix Version/s: tbd
    • Component/s: core-svc
    • Labels:
      None
    • Subcomponent:
    • CPU:
      generic
    • OS:
      generic

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                sspitsyn Serguei Spitsyn
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: