Description: I can open a LibreOffice component, calc or writer, then close it (using [CTRL + W] or the generic close button in the top right) and a "Zombie" LibreOffice process is opened and does not close, as well as the original LibreOffice and Calc processes staying alive. This new "Zombie" process consumes an odd amount of CPU resources, anywhere from 5%-15% of CPU, and ~115MB of RAM, while the original LibreOffice process consumes exactly 0 CPU and 0.9MB RAM, and the original Calc process consumes 0% CPU and 0.5MB of RAM. The "Zombie" process will run forever, bouncing between 5%-15% CPU utilization while i keep it alive. It can only be killed with the task manager, and once this process is killed, the other two original processes also close. While the zombie process is alive, no new LibreOffice processes are allowed to open, of any kind. They will "start" and can be seen in the Task manager, but will not actually open the UI until the zombie process is killed. This bug occurs in both windows 10 and 11 environments and on several different machines. I experienced it in 7.2, 7.3 and now in 7.4. If I can provide some debug report from LibreOffice, let me know. However, it does not occur on ALL of my machine running LibreOffice. It seems that at some point something in the config gets corrupt or something and then it occurs every time LibreOffice is run. Steps to Reproduce: 1. Open any LibreOffice component. 2. Close same component. Actual Results: New zombie process started and original processes still running, no new components are allowed to be started. Expected Results: Application closes completely. New components are able to be opened without issue. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 7.4.0.3 (x64) / LibreOffice Community Build ID: f85e47c08ddd19c015c0114a68350214f7066f5a CPU threads: 12; OS: Windows 10.0 Build 22622; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL Tried launching in safe mode. In safe mode, the application starts and crashes...so it made it worse. Disabling safe mode allows application to start.
In case the "Safe-mode" crashing is related, here is the event log export for that crash. Faulting application name: soffice.bin, version: 7.4.0.3, time stamp: 0x62f401e3 Faulting module name: ucrtbase.dll, version: 10.0.22621.436, time stamp: 0xf5fc15a3 Exception code: 0xc0000409 Fault offset: 0x000000000007f61e Faulting process id: 0x0x22A4 Faulting application start time: 0x0x1D8B659A5ECE055 Faulting application path: C:\Program Files\LibreOffice\program\soffice.bin Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report Id: c27f6d3d-33ac-4b0b-be9b-57e646074662 Faulting package full name: Faulting package-relative application ID:
Okay... after some more investigation, although safemode crashes for whatever reason, running with " soffice.com -env:UserInstallation=file:///c:/my-test-profile" yields the expected result and renaming my actual profile so the lo creates a new profile, does fix the issue. so it looks like "corrupt user profile" is to blame for this issue.