Hello everyone, I found that Sacado's nested reverse and forward mode AD leads to a memory leak when use multiple times. I have opened an issue on their end: https://github.com/trilinos/Trilinos/issues/7741 and the steps to reproduce are pretty simple.
However, I've found that the community here is pretty good at responding. I was wondering if anyone here has previously encountered/fixed this. I know that J-P Perlteret's code-gallery example Quasi_static_Finite_strain_Compressible_Elasticity with this AD type turned on by using set Automatic differentiation order = 2 <https://github.com/dealii/code-gallery/blob/815a7adee42bcfb4a2d8c3dd2f7de580f67e38f6/Quasi_static_Finite_strain_Compressible_Elasticity/parameters.prm#L8> does lead to a memory leak. Basically, for every cell's computation, a little bit of memory leaks, which quickly blows up for large problems. Please let me know what you think. It's likely completely in the hand of the Sacado group unless I start digging in their code. However, if it is something that will likely not get fixed, we might want to put a warning on the "Supported automatic differentiation libraries" page. Best regards, Doug -- The deal.II project is located at http://www.dealii.org/ For mailing list/forum options, see https://groups.google.com/d/forum/dealii?hl=en --- You received this message because you are subscribed to the Google Groups "deal.II User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to dealii+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dealii/9efa2b48-dd67-4a2b-ab92-0849b307b99dn%40googlegroups.com.
