New error: Resource exhausted
See original GitHub issueAfter using CARE for over 6 months all of a sudden I start getting an error when simply running model.predict:
ResourceExhaustedError: 2 root error(s) found.
(0) Resource exhausted: OOM when allocating tensor with shape[1,32,1024,1024] and type float on /job:localhost/replica:0/task:0/device:GPU:0 by allocator GPU_0_bfc
[[{{node down_level_0_no_0/convolution}}]]
Hint: If you want to see a list of allocated tensors when OOM happens, add report_tensor_allocations_upon_oom to RunOptions for current allocation info.
(1) Resource exhausted: OOM when allocating tensor with shape[1,32,1024,1024] and type float on /job:localhost/replica:0/task:0/device:GPU:0 by allocator GPU_0_bfc
[[{{node down_level_0_no_0/convolution}}]]
Hint: If you want to see a list of allocated tensors when OOM happens, add report_tensor_allocations_upon_oom to RunOptions for current allocation info.
[[concatenate_3/concat/_291]]
Hint: If you want to see a list of allocated tensors when OOM happens, add report_tensor_allocations_upon_oom to RunOptions for current allocation info.
0 successful operations.
0 derived errors ignored.
I have two GPUs in my laptop (Intel UHD Graphics 620 and NVIDIA GeForce MX130) and for some reason (maybe it always had I never checked) in the task manager and the error above tensorflow uses the Intel one.
I have tried using:
with tf.device('/gpu:1'):
a = model.predict(b, axes ='YX')
but I get the same error.
Any advice would be highly appreciated. Strange that it happens now all of a sudden since I am running it on identical size files
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
python - How I short out this error Resource Exhausted Error
I created a model with 13500 images. During the training time after 1 epoch showing an ERROR: "ResourceExhaustedError".
Read more >Receiving "Resource Exhausted" error - anyone else in the UK?
The error 'Resource has been exhausted (e.g. check quota)' comes from the google account. There are too many people trying to access that ......
Read more >resource-exhausted not retry · Issue #19789 · istio/istio - GitHub
According to the google grpc error specification, RESOURCE_EXHAUSTED is mapped to http 429. 429 indicates that the client request frequency has ...
Read more >RESOURCE_EXHAUSTED: Expected to activate jobs of type
We are getting the error of RESOURCE_EXHAUSTED: Expected to activate jobs of type in a huge amount, once I add a new worker,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Just trying to help with the above problem. I don’t have this problem with csbdeep.
Hi @joaomamede, I don’t know why you’re replying to this issue, but try this.