Created attachment 182431 [details] ZIP file containing the document I was using, the bug reports, and the "fault module" that is listed in the bug reports (note: the "fault module" only causes errors in LibreOffice, not other programs) OS: Windows 10 Home 21H2 OS Build 19044.1989 (also happened on OS build 19044.1989) LibreOffice version: 7.4.0.3 (also happened on 7.3.5.2) Note: I am not sure if this is a LibreOffice issue (since all of LibreOffice crashes) or a Writer issue (since I have only seen it crash on Writer). I am listing LibreOffice as the component since I don't know whether this bug exists on Calc and Impress. Issue: LibreOffice Writer hangs and crashes at random. This freezes almost every application including the Windows user interface. However, the computer doesn't show any signs of high CPU usage (like heating up or fans running) so this is probably LibreOffice just being idle and interfering with other programs. How to reproduce: Happens at random (usually once in one/two days) while working on larger documents like the one I am attaching named “Bug Demo” (the text is gibberish because I used “Replace All” on individual letters to get rid of the actual contents, but the layout is the same), but usually I do a lot of the following so the issue may be caused by something I am doing that most users don't do frequently like: 1. Cut-and-pasting lots of text 2. Scrolling back and forth frequently 3. Opening multiple windows for the same document for reference 4. Using extremely small font sizes 5. Leaving LibreOffice open in the background for a while without saving The following programs are affected whenever LibreOffice crashes: 1. Windows Explorer (completely freezes until either my PC somehow recovers or I do a forced shutdown. It handles the UI on Windows) 2. Windows Security (specifically the Ctrl+Alt+Del shortcut) (doesn’t respond until my PC somehow recovers or I do a forced shutdown. Under normal circumstances, it should always respond immediately and let me open Task Manager to close LibreOffice) 3. Google Chrome and Microsoft Edge (both of them freeze on-screen output until my PC somehow recovers or I do a forced shutdown, but continue playing audio) 4. RealTek HD Audio Universal Service (continues working, but audio crackles every time I try to type something on the keyboard when LibreOffice is frozen. It handles all audio output on my PC)
Hi... I spent some time messing around with your sample document (Bugs Demo.docx) and I could not notice any performance issue, not even a minor stuttering. I did a lot of scrolling up and down, copy and pasting and formatting. I did not open multiple windows with the same document though. Can you try on some other PC ? It might be something related to this specific machine you're using. System info Version: 7.3.5.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Ubuntu package version: 1:7.3.5-0ubuntu0.22.04.1 Calc: threaded
(In reply to Rafael Lima from comment #1) Sorry, but I don't have access to another PC for testing LibreOffice, especially for more than a full day which is how long it takes for it to crash. The following is my system info: Version: 7.4.0.3 (x64) / LibreOffice Community Build ID: f85e47c08ddd19c015c0114a68350214f7066f5a CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: default; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded I think this might be a Windows-specific issue since according to Windows' Reliability Monitor, LibreOffice crashed while using a Windows system file. That file hasn't been modified since last year, and the bug started 1 or 2 weeks back, so I think this bug is *not* due to the Windows system file.
(In reply to mvk1234321 from comment #2) > I think this might be a Windows-specific issue since according to Windows' > Reliability Monitor, LibreOffice crashed while using a Windows system file. > That file hasn't been modified since last year, and the bug started 1 or 2 > weeks back, so I think this bug is *not* due to the Windows system file. Okay... let's wait and see if someone can test this bug on Windows. This might be windows-related.