No, that was a separate issue related to DNS traffic. And the fix for that does nothing to affect this problem.

FB12220519

Any time includeAllNetworks is set in the protocol configuration, and the shutdown is initiated from the extension, and concludes with a call to cancelTunnelWithError, then we see the problem