Description: Noticeable at least at a7ce8404befaf59df5f1a476c8dd414633bbf823 . (Will check whether possibly has gone away since.) Will attach a zip archive with reproduction executable. - Build LO with debugging symbols - Start it, instdir/program/soffice - Attach it in VS - In another Cygwin shell, go to where this zip is unpacked and run: THISDIR='c:/where/ever/this/is/' ./BugReproducer.exe After the "Closing document" you will see the abort() hit in VS. Steps to Reproduce: . Actual Results: . Expected Results: . Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/604.1.38 (KHTML, like Gecko) Version/11.0 Safari/604.1.38
Created attachment 136526 [details] Reproducer
I just get a "Open calc /srv/dev/COM-bug/BugReproducer.xls", but nothing else happens. I also tried starting LO with "make debugrun" - no change. THISDIR="$(pwd)/" ./BugReproducer.exe
I don't think $(pwd) will work as is a Cygwin-format pathname? (Hmm, or does Cygwin automatically translate it to Windows format before exporting to the Windows process?) I guess one possibllity is that some Registry magic is not present on that machine; have you even installed LO from an installer on it? I am not entirely sure how the COM stuff works. But presumably some magic in the Registry takes care of the fact that the source code of the program contains only "com.sun.star.ServiceManager" and somehow that is supposed to make it contact the running soffice.bin.
To get a Windows patch, the correct call is actually THISDIR="$(cygpath -w -a -l $(pwd))\\" ./BugReproducer.exe
Jan-Marek Glogowski committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=d21212cadebad682e7e3cce2b93b7d9a6ee1e1ec tdf#112646 Flush the clipboard holding SolarMutex It will be available in 6.0.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.
A polite ping to Jan-Marek Glogowski: is this bug fixed? if so, could you please close it as RESOLVED FIXED ? Thanks