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.