Arnold memory leak - running standalone Arnold as a solution?

designimation
Enthusiast

Arnold memory leak - running standalone Arnold as a solution?

designimation
Enthusiast
Enthusiast

As others have reported, I'm encountering a memory leak and render times increasing greatly during the course of a GPU render sequence.  This is with Maya 2023.1.  I haven't found any consensus on a solution.

 

I found a reddit thread from 2018 where a user describes definitively fixing the issue by using the standalone Arnold.

 

Just wondering if anyone can comment on that.  I've seen other contradictory reports that Arnold only works via MtoA.

Reply
Accepted solutions (1)
1,177 Views
5 Replies
Replies (5)

designimation
Enthusiast
Enthusiast
Accepted solution

As reported in the forum, this is a known bug and the (relatively) easy solution is to revert to using Maya 2022.1.

 

It's been years - sure wish Autodesk would finally get the GPU renderer to have parity with the CPU in terms of features and reliability.

dalecampbelljrLUC83
Contributor
Contributor

Is this an issue still in the 2023.3 update just released?

0 Likes

Stephen.Blair
Community Manager
Community Manager

@dalecampbelljrLUC83 wrote:

Is this an issue still in the 2023.3 update just released?


2023.3 doesn't have the most recent Arnold. We had to hand off a version of MtoA to the Maya team, and since then we released MtoA 5.2.2 and MtoA 5.2.21

 

I don't think we've ever reproduced this memory leak. For the first couple of frames, yes, but not enough to use up all available memory.

See https://forums.autodesk.com/t5/arnold-for-3ds-max/gpu-memory-not-freeing-up-after-render/m-p/1160299...



// Stephen Blair
// Arnold Renderer Support

designimation
Enthusiast
Enthusiast

Hi Stephen.

 

Do you want me to send you my archived scene file with the GPU leak?

 

-michael

0 Likes

dalecampbelljrLUC83
Contributor
Contributor

I would like to see it if you don't mind.

0 Likes