Did you click on the link?

A number of operations have backwards that use atomicAdd , in particular  torch.nn.functional.embedding_bag()  2,  torch.nn.functional.ctc_loss()  and many forms of pooling, padding, and sampling. There currently is no simple way of avoiding non-determinism in these functions.

From a cursory reading of the code, you use pooling.
Best regards
Thomas