Maybe something to do with re-initializing the interpreter messing up the optimizer state?
Maybe something to do with re-initializing the interpreter messing up the optimizer state?