Hello Joakim, > Le 3 nov. 2019 à 23:25, Joakim Dahlgren Strandberg <joaki...@kth.se> a écrit : > > Hi Pascal, > > Thanks for the detailed analysis of the potential memory leak. Seems it was a > treasure trove of issues to look at. I suspected there may be something > suspicious with some code in Dmitry's Simple Components but the code I looked > at appeared correct. Looking forward to hear more about the progress on this. > If I find out more I will share it here on the Gnoga mailing list of course. > > Best regards, > Joakim > ________________________________________
... > Hello Joakim, > > I have got detailed results from valgrind of memory leaks after Gnoga server > execution. > There is 4 kinds of them: > - allocation in globals that are not freed before exiting (Watchdog and > Gnoga_HTTP_Server) -> easy to fix Fix. > - allocation in GNAT RTE (initialization, Unbounded_String, String, > String_Access and exceptions) -> to be reported to AdaCore Done for Unbounded_String. > - allocation in HTTP server (container) -> to be reported to Dmitry Fix. > - allocation in Multi-Connect application for Connection_Data, user guide > said: > -- By default Connection_Data is assumed to be a dynamic object > -- and freed when the connection is closed. > but it seems not to be the case -> investigation is needed. Added a log: "Connection_Data freed", it seems then to be correct. Changes are commited: https://sourceforge.net/p/gnoga/code/ci/8bf88ff3c965689b2f097d1f4b0aab69cc75f9bd/ Could you please check with valgring if these leaks are still present or not? Thanks, Pascal. http://blady.pagesperso-orange.fr _______________________________________________ Gnoga-list mailing list Gnoga-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnoga-list
