[KevinH]

And yes theducks, this bug was "fixed" once before (the comments in the FlowTab destructor are clear on this) but for some reason the simple disconnect that used to fix the problem is now not working or returns before it completes and an explicit disconnect seems to be needed to prevent the flow tab that is being destroyed from being reentered.

Thus the quick patch as I had seen this same bug earlier and thought I had nipped it in the bud, so I am are trying again. The second disconnect may just cause a long enough delay so that the first attempt at full disconnection works but it certainly can not hurt and seems to "fix the problem" on my machine.