I seem to have found another wierd quirk in CUDA 1.1. For some reason my program has just started producing out of memory errors when I call cudaMallocHost. It doesn’t do it all the time though. Is there some way of monitoring the memory available for this? Is it possible I have hit some other limit? I have several buffers allocated this way but they total less than 4MB. I do free and reallocate them from time to time - is it possible this is going wrong somewhere? How do I troubleshoot the problem?
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| cudamallochost problem | 6 | 10805 | March 10, 2011 | |
| cudaMalloc Limit | 2 | 2757 | July 17, 2008 | |
| cudaMallocHost crash since update from cuda 7.0.28 to 8.0.44 | 5 | 1378 | July 31, 2017 | |
| cudaMallocHost not returning errors in emulation mode | 1 | 1471 | June 3, 2009 | |
| Should cudaMallocHost() need retry? | 4 | 1277 | January 10, 2016 | |
| Problem CudaMallocHost | 4 | 2074 | July 14, 2015 | |
| 1st call to cudaMallocHost fails... ... but next calls are OK. (!?) | 1 | 6156 | January 8, 2009 | |
| Cuda Out of Memory with tons of memory left? | 5 | 38980 | December 23, 2009 | |
| cudaHostAlloc not consistent between CUDA 3.0 beta 1 and CUDA 3.0 | 0 | 1268 | April 16, 2010 | |
| Out Of Memory Error Allocating large chunks (> 1GB) of pinned-memory fails | 3 | 5847 | June 4, 2011 |