Duplication handling and optimization of CaptureCallState

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P4
    • 25
    • Affects Version/s: 25
    • Component/s: core-libs
    • None

      In a previous optimization of captureCallState, the optimization incorrectly handled potentially duplicate values, and seems the toString message is affected too. We can remove the stream usage for CaptureCallState. Also we can remove the redundant initialization overhead of OperatingSystem.isWindows.

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

              Created:
              Updated:
              Resolved: