Debugger very slow during stepping

XMLWordPrintable

    • Type: CSR
    • Resolution: Withdrawn
    • Priority: P3
    • 26
    • Component/s: hotspot
    • None
    • behavioral
    • minimal
    • This can potentially break user expectations/assumptions about target thread execution mode because enabling JVMTI FramePop events do not enforce `interp-only` execution mode for target thread. Instead, the only one target frame is kept interpreted.
    • Other

      Summary

      Enabling JVMTI SingleStep events do not enforce interp-only execution mode anymore.

      Problem

      Enforcing the interp-only execution mode to support JVMTI SingleStep events causes significant execution slowdown (~20X).

      Solution

      Do not enforce interp-only execution mode to support JVMTI SingleStep events. Instead, just deoptimize target frame and disable OSR (On Stack Replacement) optimization on it, so that it is kept interpreted. This allows to execute in a compiled mode other methods recursively called from this frame.

      Specification

      N/A - the specification has not been changed. This may need a Release Note.

            Assignee:
            Serguei Spitsyn
            Reporter:
            Martin Entlicher
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: