apparently some of the tests that run during the build leave files in /tmp that they really should delete. somebody should find out which tests are responsible for that and which cleanup function needs to be called.
to narrow down the culprits build individual modules, then comment out some of the CppunitTests in Module_*.mk and finally investigate the source of the tests that are responsible (look at the CppunitTest_*.mk files to find the cxx source files).
Miklos fixed already a large number of these leaked files during the hackfest: http://cgit.freedesktop.org/libreoffice/core/commit/?id=c03a1e46460e4255d7709df9ba8147947f66acfb
adding LibreOffice developer list as CC to unresolved EasyHacks for better visibility. see e.g. http://nabble.documentfoundation.org/minutes-of-ESC-call-td4076214.html for details
I am interested in working on this. I am a beginner in C++ (university student) and new to LibreOffice, and open source in general. Is there a primary contact I can reach out to if I need some pointers/help? Thanks a lot!
(In reply to comment #4) > Is there a primary contact I can reach out to if I need some pointers/help? The best way is to ask on IRC: #libreoffice-dev on FreeNode.
I would like to fix this bug.
Migrating Whiteboard tags to Keywords: (easyHack, difficultyBeginner, skillCpp) [NinjaEdit]
JanI is default CC for Easy Hacks (Add Jan; remove LibreOffice Dev List from CC) [NinjaEdit]
I fixed two temp file leaks in sw tests, submitted patch to gerrit. There is one more leak left in sw/qa/extras/uiwriter.cxx SwUiWriterTest::testEmbeddedDataSource but I do not know how to fix it. I found that the leaked file is created after executing these lines: uno::Reference<sdbc::XDataSource> xDataSource(xDatabaseContext->getByName("calc-data-source"), uno::UNO_QUERY); CPPUNIT_ASSERT(xDataSource.is()); uno::Reference<sdbcx::XTablesSupplier> xConnection(xDataSource->getConnection("", ""), uno::UNO_QUERY); but I do not see anything related to disposal in XComponentContext or XDataSource.
I fixed temp file leaks in sc tests, now make sc.check does not leave any temp files. Submitted patch to gerrit.
Aleksas Pantechovskis committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=14c14094e8587d28eb9cd2a3b5c0c57b355635b5 tdf#65219 Fix temp files clean up in sc unit tests It will be available in 5.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
I fixed temp file leaks in sd tests, submitted patch to gerrit. There are two more leaks left in sd/qa/unit/mist-tests.cxx, but so I have not figured out how to fix it yet. As far as I identified the file is created after executing this line: xSSController.GetClipboard().DoPaste();
Aleksas Pantechovskis committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=123b41c3870810d61fde5e17c74a352e3fd2a694 tdf#65219 Fix temp files clean up in sw unit tests It will be available in 5.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Aleksas Pantechovskis committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=080f355f11ee3422e9512815efd9f8d7eb896d32 tdf#65219 Fix temp files clean up in sd unit tests It will be available in 5.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Seems solved