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.

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

week4: Memory problem #43

Open
NickVeld opened this issue Oct 7, 2019 · 1 comment
Open

week4: Memory problem #43

NickVeld opened this issue Oct 7, 2019 · 1 comment

Comments

@NickVeld
Copy link
Contributor

NickVeld commented Oct 7, 2019

Google Collab:

CPU

100-th iteration kills runtime with "unknown reason"

CUDA

 0%|          | 110/25000 [00:01<05:47, 71.73it/s]
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
<ipython-input-19-adef1f515998> in <module>()
     26 
     27         # use your embedding model to produce feature vector
---> 28         features = embedding(input_tensor) #<YOUR CODE>
     29 
     30         X.append(features)



3 frames

/usr/local/lib/python3.6/dist-packages/torch/nn/functional.py in _max_pool2d(input, kernel_size, stride, padding, dilation, ceil_mode, return_indices)
    485         stride = torch.jit.annotate(List[int], [])
    486     return torch.max_pool2d(
--> 487         input, kernel_size, stride, padding, dilation, ceil_mode)
    488 
    489 max_pool2d = boolean_dispatch(

RuntimeError: CUDA out of memory. Tried to allocate 28.00 MiB (GPU 0; 11.17 GiB total capacity; 10.70 GiB already allocated; 5.81 MiB free; 141.58 MiB cached)
@NickVeld
Copy link
Contributor Author

NickVeld commented Oct 7, 2019

CUDA case was fixed by transforming Tensor to ndarray, may be it helps for CPU case

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant