-
Notifications
You must be signed in to change notification settings - Fork 71
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
Out of memory errors don't work properly #496
Comments
Seems the problem was introduced here: |
@llaniewski it is probably a different bug, but some things still don't work as expected (also the same on The error is the same even if try I split between 3 GPUs (40GB each, so plenty of space even if there is some unaccounted memory) |
@shkodm Just to clarify, do these large cases run on the |
@llaniewski no, they also don't work on master branch. The error happens in the |
Closing this issue and moving the discussion of the size limitation to #499 . Addressing it is a bigger thing and wound need testing of performance. |
Found on
develop
branch when trying to run large example (automatically generated).Can, for instance, can be reproduced:
256 x 512 x 256:
[ ] [0] Cumulative allocation of 168231424 b (30.2 GB)
Works fine256 x 800 x 256:
Cumulative allocation of -24577536 b (18446744073.7 GB)
Throws out of memory error correctly, but incorrect reporting of total allocated memory.512 x 800 x 256: Tries to allocated incorect (much smaller) total amount of memory and throws a different error:
Expected behaviour: correct memory allocation is reported, and correct error is throws (the behaviour of
master
branch). Probably related to some casting or overflowThe text was updated successfully, but these errors were encountered: