tree 7bd3c45b344dcb21a558fbd0e635034eefba82fd
parent b42b59020e6e3ad92a1db045b73b051e47bacd10
author Alon Zakai <azakai@google.com> 1608164234 -0800
committer GitHub <noreply@github.com> 1608164234 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJf2qOKCRBK7hj4Ov3rIwAAdHIIAAueLfw5a84mBZOfRJFv9qDY
 wfyGNRTaZE+VAZzXeVSQQjXLX5YSvxbXo2/p3pNEccLpOuGW0kVFoAb91tiRGDwW
 8E0StW4PLgvC7fqW8BbGCBu/dVo5JWyfQXG710NXCXjL6EcmhQJPuEK7/5w1qcgY
 9au12FZb6Zo1W9z6aGcpihwZgJFOFYzv178YWKOTiH5DwEi52DN2BWIYDkdCQjKB
 Z2nHUvWe5KQRt807qzDGVqHI2UPC9b54Wk5YabphIDHOsE3POF1UHLNFEF2aaUsm
 SGql03bD3v4B3Er6cAxt7PECQKpUnHfMeKWxj13EX5VxUB+K8SjSoN8+A9H6LNE=
 =ivhM
 -----END PGP SIGNATURE-----
 

[Dylink] Remove a racy assertion (#13060)

If 2 side modules are loaded, A and B, and loadModule is called on A, then B,
then it is possible that if instantiation is done async here then the
postInstantiation() callbacks may happen in the reverse order, racily. If that
happens, the extra assertions on the table not changing can fire incorrectly -
the other parts of the table will appear to have changed meanwhile, but for
valid reasons.

Fixes #13054
Fixes #11458