Has the upgrade in the past two years solved any problem of memory leaks?

We used Dynet to build a semantic role labeling model consisting of multiple LSTMs. During the long-term deployment and prediction of the model deployment online, the memory continues to increase and maybe there is a memory leak somewhere in dynet.

The code calling dynet is at https://github.com/HIT-SCIR/ltp/tree/master/src/srl. (the exact location is unknown. We have checked our code and all 'new's have been handled well.)

Our dynet version is a copy at https://github.com/HIT-SCIR/ltp/tree/master/thirdparty/dynet two years ago.We have try to use dynamic and static memory check tools but found nothing.

Is there anyone else who ever experienced the same problem? Is there any fix about some bugs like this, and whether this will be solved if we just update our dynet copy version.

Looking forward to your reply. Thank you.

Start with the calling code under ltp/src/srl and the copied DyNet code under ltp/thirdparty/dynet, then compare that snapshot with a newer DyNet version. Reproduce the long-term LSTM deployment while monitoring memory, and document whether the issue persists and whether an update changes the result.

Written by the indexing model from the issue text.