Hi @michaelmueller1994, you can safely ignore it, as the error only occurs when PyTorch is done running and Python is unloading the modules. It doesn’t impact the models at all, and the issue has been fixed in the PyTorch wheel that will be posted in the upcoming JetPack 4.4 production release. Apologies for the inconvienience.