https://bugs.documentfoundation.org/show_bug.cgi?id=41288
--- Comment #17 from WCDR <wizardco...@yahoo.fr> --- Tested in November 2023: Ubuntu 20 with LO v6.4.7.2 and 7.5.8.2. > Still there via a C++ call. An easy way to generate the problem is to use the example provided with the SDK: https://api.libreoffice.org/examples/cpp/DocumentLoader/ 1 - on T1 : libreoffice "--accept=socket,host=localhost,port=2083;urp;StarOffice.ServiceManager" 2 - Run ubuntu "system monitor" with a "soffice" filter 3 - Note the memory value ~ 50Mb 4 - On T2 run the sample with the sample provided or the document I have attached. 5 - Note the memory value 6 - Repeat steps 4-5-... After 1000 tasks, the process memory usage is ~ 1.2 Gb Add: xComponent->dispose (); after loadComponentFromURL helps a little, but not that much. If you put a loop around loadComponentFromURL, you have the same problem, the problem seems to be located in the code behind loadComponentFromURL. Removing the loadComponentFromURL line removes the leak... Even when waiting, memory consumption doesn't decrease... This bug is a real problem, because having to close the process and reopen it takes an enormous amount of time that is not compatible with microservice architecture, and the size of the leak is a problem for the sizing and the execution environment. If I can help by doing some tests, I'm finishing compiling libreoffice-core today... however, I don't do Python... Regards -- You are receiving this mail because: You are the assignee for the bug.
