I am. At least, I tried on cpu, and the issue either occurs on a different episode (or possibly doesnt occur; unclear)
I’ll set deterministic to True, and see what happens.
Unfortunately, I haven’t managed to create a small reproducible snippet, since all my attempts to freeze a single training step that reproduces the error have failed to date, and the surrounding code is fairly complex.
Good heads-up on the deterministic=True. Thanks!