Its stack trace in Figure 6 confirms why this plug-in was activated after the workbench window opened.

The stack reacts to the timeout by resetting the congestion window back to an empty state.