Quantcast
Channel: AI Beta - Unity Discussions
Viewing all articles
Browse latest Browse all 109

MakeReadable() possible memory leak

$
0
0

I’m running a network every frame with a fairly large output tensor ((56x80x80) - I mention this because the leak is much more apparent with large outputs), and found that outputTensor.MakeReadable() steadily increases my program’s memory use each frame. When I remove this line the memory use is constant, however I need to be able to do further calculations on the cpu.

I initialize the output tensor with the “using TensorFloat …” statement as in the examples. The only difference is just the network and having worker.Execute() and worker.PeekOutput() in the Update() call.

Thanks!

8 posts - 4 participants

Read full topic


Viewing all articles
Browse latest Browse all 109

Trending Articles