-
-
Notifications
You must be signed in to change notification settings - Fork 16.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error when "torch.load()" #581
Comments
@sveits6 I don't recognize that command, and we don't assist in debugging custom code. |
Hello, @glenn-jocher, I am having the same issue. It happens with the new v2.0, when starting a training in the ultralytics docker container. I pulled the latest container and started a training. It starts to download the pt file (yolov5m.pt) and then errors out:
Were those new weights trained with pytorch 1.6? The docker container uses 1.5.x Greetings and Thanks, |
Just checked it, by installing torch==1.6.0 and torchvision==0.7.0. |
@mfruhner thanks! Yes we are in the process of updating requirements.txt to 1.6, and will be pushing native mixed precision training PR as well. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This solved my same problem |
❔Question
Traceback (most recent call last):
File "D:\Envs\pyt1.4\lib\site-packages\torch\serialization.py", line 527, in load
with _open_zipfile_reader(f) as opened_zipfile:
File "D:\Envs\pyt1.4\lib\site-packages\torch\serialization.py", line 224, in init
super(_open_zipfile_reader, self).init(torch.C.PyTorchFileReader(name_or_buffer))
RuntimeError: version <= kMaxSupportedFileFormatVersion INTERNAL ASSERT FAILED at ..\caffe2\serialize\inline_container.cc:132, please report a bug to PyTorch. Attempted to read a PyTorch file with version 3, but the maximum supported version for reading is 2. Your PyTorch installation may be too old. (init at ..\caffe2\serialize\inline_container.cc:132)
(no backtrace available)
How to solve it?This just happen on the newest weights file of your google drive.The weights file of last version is ok.
Additional context
The text was updated successfully, but these errors were encountered: