https://bugs.documentfoundation.org/show_bug.cgi?id=93116
--- Comment #8 from [email protected] --- I wrote much fewer than before in the last ten days. I tried to open many files (odt, odc, odp, odb) and closed them , no multiple instances occured. I did not edit files. That is, I did not test under a complete conditions. Then I installed activex controller, explorer extension, English and German dictionary again. No quickstart is installed. My Asus Laptop runs "Instant On" program so that it did not enter into hibernation, rather into stand by. This is what I used everyday. I must correct what I have said. I let process explorer open everyday in order to see whether mutiple instances occur. Today I encountered an invisible instance. Libreoffice： 5.0.1.1 (x64), Windows 8(x64) The first set One odt file was edited (simply entered words, went around, deleted, copied, pasted, ctrl-s (saved)) last night. soffice.exe and soffice.bin were in memory. This was the first set. Entered into stand-by last night. Resumed from stand-by today. soffice.exe's command line: "C:\Program Files\LibreOffice 5\program\soffice.exe" soffice.bin's: "C:\Program Files\LibreOffice 5\program\soffice.exe" "-env:OOO_CWD=2C:\\Program Files\\LibreOffice 5". It consumed about 60 MB. The second set Right-clicked another odt file in Windows explorer today. It was not opened. Another set of LO program appeared in memory: swriter.exe, soffice.exe, soffice.bin. This is the second set. Soffice.bin is invisible on screen and its memory consumption is much smaller, about 5 MB. swriter.exe's command line: "C:\Program Files\LibreOffice 5\program\swriter.exe" -o "pathname", soffice.exe's: "C:\Program Files\LibreOffice 5\program\swriter.exe" -o "pathname" --writer, soffice.bin's: "C:\Program Files\LibreOffice 5\program\swriter.exe" "-o" "pathname" "--writer" "-env:OOO_CWD=2filepath" (where instead "\", "\\" were used) Open file from within Tried to open another odt or ods file from within LO through "File > open" or "file > recent documents", it succeeded. No other set(swrite.exe/scalc.exe, soffice.exe, soffice.bin) was created. Soffice.bin in the first set consumed more memory now while the memory consumption of the second set remained no change. Open file from outside Now right-clicked another odt file in Windows explorer. I thought it should not be opened in this way, but it was opened. It seems that the last successful opening changed the status. The second set remained unchanged in its memory consumption. Close the first set with ctrl-q I closed (visible) LO with ctrl-q. The first set disappeared from memory. The second set remained. The third set Right-clicked an odt file in Windows explorer. It was opened. Another set appear in memory. Details of command lines: swriter.exe: "C:\Program Files\LibreOffice 5\program\swriter.exe" -o "pathname" soffice.exe: "C:\Program Files\LibreOffice 5\program\swriter.exe" -o "pathname" --writer "C:\Program Files\LibreOffice 5\program\swriter.exe" "-o" "pathname" "--writer" "-env:OOO_CWD=2filepath" This is different from the first set because the file is opened from outside. If it is opened from within soffice, the set shall be similar that of the first. With ctrl-q, LO is quitted. The third set disappeared from memory. The second remained in memory. The fouth set Clicked soffice icon and opened an odt file from within. It succeeded. The fouth set appeared in memory. With ctrl-q, LO is quitted and the fourth set disappeared from memory. The second set remained. The fifth set Right-clicked an odt file in Windows explorer. It was opened successfully. Soffice.bin's threads are as follows: Soffice.bin threads (succeeded to open odt by right click odt in Win Explorer).png It differed in considerable degree from soffice.bin's threads in the second set which showed in the attached picture: Soffice.bin threads (faileded to open odt by right click odt in Win Explorer).png. Entered into stand by. Resumed from it. Right-clicked an odt file in Windows explorer. It was opened successfully. No other set appeared in memory. It was not more than two sets of LO processes in memory. But I have seen more than two sets in memory. I guess that procedure to generate more than two sets differed in steps from the above mentioned. For the first (invisible) set stack of thread 5416 swriter.exe+0x1388 (almost the same with that of a noraml set) ntdll.dll!NtWaitForSingleObject+0xa KERNELBASE.dll!WaitForSingleObjectEx+0x9a swriter.exe+0x1964 stack of thread 4860 sofice.exe+0x24f4 (almost the same with that of a noraml set) ntdll.dll!NtWaitForMultipleObjects+0xa KERNELBASE.dll!GetTickCount+0x4e USER32.dll!GetWindowLongPtrA+0x21a soffice.exe+0x1bbc soffice.exe+0x240e KERNEL32.DLL!BaseThreadInitThunk+0x1a ntdll.dll!RtlUserThreadStart+0x21 stack of thread 4752 !main+0x200 (differs in considerable degree from that of a noraml set) (Not "soffice.bin!main+0x200", just "!main+0x200". Without "soffice.bin". See Soffice.bin (failed ...) thread main stack.png. !RtlCommitDebugInfo+0x84 seems to increase in thread number with every looking in.) !NtWaitForSingleObject+0xa !RtlMultiAppendUnicodeStringBuffer+0x38e !RtlInitializeCriticalSection+0x125 !RtlGetOwnerSecurityDescriptor+0x137 !CommandLineToArgvW+0x10e3 !SHGetFolderPathW+0x19b !PathIsExeWorker+0x4174 !PathIsExeWorker+0x3f4d !PathIsExeWorker+0x5995 !PathIsExeWorker+0x49d7 !PathIsExeWorker+0x623d !SHCoCreateInstanceWorker+0x1180 !SHGetFolderPathEx+0x80 !SHGetFolderPathWWorker+0x101 !SHGetFolderPathW+0x49 !SHGetFolderPathAWorker+0x40 !SHGetFolderPathA+0x43 !SHGetSpecialFolderPathAWorker+0x27 !SHGetSpecialFolderPathA+0x3b !osl_writePipe+0x254 !osl_getConfigDir+0x67 !rtl_reallocateMemory+0x670a !rtl_reallocateMemory+0x6c47 !rtl_reallocateMemory+0x5674 !rtl_reallocateMemory+0x7383 !rtl_reallocateMemory+0x582c !rtl_reallocateMemory+0x5c6e !rtl_reallocateMemory+0x68b1 !rtl_reallocateMemory+0x6c47 !rtl_reallocateMemory+0x52ef !rtl_bootstrap_expandMacros+0x3c !EmbeddedFontsHelper::clearTemporaryFontFiles+0x4b !InitVCL+0x3b !DeInitVCL+0x6e4 !SVMain+0x32 !soffice_main+0x75 !main+0x35d !BaseThreadInitThunk+0x1a !RtlUserThreadStart+0x21 a normal (visible) set stack of thread 2384 swriter.exe+0x1388 ntdll.dll!NtWaitForSingleObject+0xa KERNELBASE.dll!WaitForSingleObjectEx+0x9a swriter.exe+0x1964 stack of thread 5566 soffice.exe+0x24f4 ntdll.dll!NtWaitForMultipleObjects+0xa KERNELBASE.dll!GetTickCount+0x4e USER32.dll!GetWindowLongPtrA+0x21a soffice.exe+0x1bbc soffice.exe+0x240e KERNEL32.DLL!BaseThreadInitThunk+0x1a ntdll.dll!RtlUserThreadStart+0x21 stack of thread 5308 soffice.bin!main+0x200 USER32.dll!IsThreadDesktopComposited+0x2fa USER32.dll!GetMessageW+0x25 mergedlo.dll!vcl::IsWindowSystemAvailable+0x7439 mergedlo.dll!vcl::IsWindowSystemAvailable+0x7eac mergedlo.dll!Application::Execute+0x7e mergedlo.dll!cppu::WeakImplHelper2<com::sun::star::lang::XServiceInfo,com::sun::star::frame::XTerminateListener>::operator=+0x4648 mergedlo.dll!DeInitVCL+0x6f9 mergedlo.dll!SVMain+0x32 mergedlo.dll!soffice_main+0x75 soffice.bin+0x102e soffice.bin!main+0x35d KERNEL32.DLL!BaseThreadInitThunk+0x1a ntdll.dll!RtlUserThreadStart+0x21 As having already seen, I could not reproduce the steps for bug-occurence. Thank you for your patience for reading this to end. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
