https://bugs.documentfoundation.org/show_bug.cgi?id=161048
--- Comment #10 from ady <[email protected]> --- (In reply to Mike Kaganski from comment #8) > ady, can you please: > > 1. Check which command line is reported in Windows Task Manager for the > leftover process? You might need to enable "Command line" column in Details > tab for that. The command line may be long. LibreOfficeDev_24.8.0.0.alpha0_Win_x86-64.msi built 2024-05-13 downloaded from TB77. Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 0dcaff6043e1f24ce0fa354dff80a86e40622247 CPU threads: 4; OS: Windows 10 X86_64 (10.0 build 19045); UI render: Skia/Raster; VCL: win Locale: es-AR (es_AR); UI: es-ES Calc: CL threaded When first launching LO Dev, Task Manager shows 1 _background_ Process line (I find the background detail unexpected; for soffice.exe) and 1 active Process line (for soffice.bin). Command lines in TM are as follows: * soffice.exe: "D:\LO\ALPHA\program\soffice.exe" * soffice.bin: "D:\LO\ALPHA\program\soffice.exe" "-env:OOO_CWD=2D:\\D\\ALPHA\\program" If I also open some ods file, a sub-process is listed under the active LibreOfficeDev line (corresponding to soffice.bin); no command line listed for this sub-process. Closing the ods file (so only the Start Center is left open), the sub-process is still listed in the same place, under the active LibreOfficeDev process. Once I close the Start Center, the sub-process is not there anymore (or I don't see it anywhere), and both LibreOfficeDev processes are shown under the background Processes. The command lines are the same as before. In Task Manager, soffice.exe is left with 0.5MB of RAM in use, and soffice.bin is left using 93.6MB of RAM, according to Task Manager; the specific amount changes according to how many times I launched LO Dev. If I use menu Help > Restart in Safe Mode, LO Dev does not automatically restarts. If I run soffice.exe again, the expected wizard for Safe Mode is launched. Once I reset to defaults in the wizard, the restart automatically launches the normal Start Center. Once closing all, I am left with multiple background processes (a pair for every launch). > > 2. Use > https://wiki.documentfoundation.org/ > How_to_get_a_backtrace_with_WinDbg#Producing_a_mini_dump to produce a > minidump of the leftover BIN process. Is this the same as saving a dump from Task Manager? After closing LO Dev, the dump for soffice.bin from TM is near 600MB. If I still need to create a new dump as described in that wiki page, I would like to know, which executable file should I use: procdump.exe, procdump64.exe, or procdump64a.exe? In addition, do I need to install WinDbg and follow the whole set of instructions? I have some limitations to what I can do in this system, so I might not be able to complete the instructions. Hopefully the info I already provided is enough for someone more capable to replicate the problem (which does not happen with LO Dev from just a few days ago, and does not happen when reinstalling that same build over the new one). -- You are receiving this mail because: You are the assignee for the bug.
