https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80477
--- Comment #6 from Stefano Zaghi <stefano.zaghi at cnr dot it> --- Dear Janus, thank you very much for your help, it is really appreciated. > Note that most gfortran developers actually sacrifice their spare time to > contribute, without receiving any kind of financial reward for it. > I contributed large parts of the OOP implementation when I was a student > (with some funding via GSoC). Nowadays my day job and private life keeps me > from spending too much time on gfotran, but I still try to contribute the > occasional bug fix if I can. As I tried to clarify to Steve, mine was absolutely not a polemic question: although my contributions are definitely not equal to yours, I am also an active FOSS developer doing things for the community spending my free time, I clearly understand the FOSS developing effort. What I meant was "because the bug is known from 2014, can I conclude that there are not any developer who takes care (for time/interest lacking) about this in a reasonable time?". It is just a hint-request about a roadmap (I have to decide how to progress my work, gnu was a key feature), absolutely no critics about you, you are my superheros. My concern was that the bug was very difficult to solve and you are too few to solve it. I am going to create a detailed report (within a github repository) taking into account many combinations: it seems that if I add an allocatable component alongside the static one, the leaks disappear (although this does not happen in a real,omplex code where both static and dynamic components are present). If it is of some help, I would like to share with you. My best regards.
