Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Non-OOM error can happen during patch size finder #360

Closed
qin-yu opened this issue Nov 21, 2024 · 1 comment
Closed

Non-OOM error can happen during patch size finder #360

qin-yu opened this issue Nov 21, 2024 · 1 comment
Assignees
@qin-yu
Labels
bug Something isn't working

Comments

@qin-yu
Copy link
Collaborator

qin-yu commented Nov 21, 2024 •
edited
Loading

Similar to #358

RuntimeError: upsample_nearest3d only supports output tensors with less than INT_MAX elements, but got [1, 32, 416, 416, 416] can happen for large VRAM devices during find_a_max_patch_shape

reported also by @AlexisMaizel with the log file: 20241119.log
@qin-yu qin-yu self-assigned this Nov 21, 2024
@qin-yu qin-yu added the bug Something isn't working label Nov 21, 2024
@qin-yu
Copy link
Collaborator Author

qin-yu commented Nov 25, 2024

Fixed by #361

@qin-yu qin-yu closed this as completed Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@qin-yu qin-yu

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@qin-yu