https://bugs.freedesktop.org/show_bug.cgi?id=56511
--- Comment #3 from Horst Reiterer <horst.reite...@fabasoft.com> --- Thanks for your input, Stephan. I'm positive the file descriptor leak did not exist before. We're using a socket-based UNO connection, I'm afraid the workaround of naming the connection endpoint does not apply in that case. I can reproduce the leak using the DocumentLoader sample provided in the SDK. After adding a missing dispose of the loaded document returned by loadComponentfromURL, one socket leaked by UNO on the server-side per execution remains: make DocumentLoader.run ll /proc/17114/fd|grep socket # ... lrwx------. 1 root root 64 May 16 14:27 91 -> socket:[341977618] lrwx------. 1 root root 64 May 16 14:34 910 -> socket:[341995066] lrwx------. 1 root root 64 May 16 14:34 911 -> socket:[341995118] lrwx------. 1 root root 64 May 16 14:39 912 -> socket:[341995166] lrwx------. 1 root root 64 May 16 14:34 913 -> socket:[341995260] lrwx------. 1 root root 64 May 16 14:34 914 -> socket:[341995308] # ... I started LibreOffice as follows: /opt/libreoffice4.0/program/soffice --nofirststartwizard --nologo --headless --norestore --invisible "--accept=socket,host=localhost,port=2083,tcpNoDelay=1;urp;" Please look into it. IMHO, this is a serious issue for anyone who uses LibreOffice via UNO. For now, we worked around the issue by restarting the instance periodically. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
