I work in Windows 10/ Libre Office 126.96.36.199 / Embedded Firebird… but similar problems go back years.
This is a poor question because I can’t give you the exact steps to get the crash. If I knew, I wouldn’t take them!
But it happens regularly. And is extremely disruptive, if you don’t know how to recover from it. (Merely “very disruptive” if you do.)
It may not be specific to these circumstances, but I seem to get hit by it most often when editing reports (and forms, tables, etc) in Base. They rarely if ever happen if I am in any other component of LO.
To get out without a full reset of my Windows… sometimes only otherwise possible with a long-press of the computer’s on/off button… open Task Manager. (Ctrl-Alt-Del will give you a way to do that.)
Under “Processes” click in any Libre Office lines, and then do “End Task”… one at a time. If one doesn’t do anything, try another until they are all gone. This will shut down any open LO document. You won’t get a chance to save unsaved work.
Your machine should work again now. Without a Windows restart (^_^).
I have no other app that regularly brings all of Windows down. I don’t think LO does this when I am using only Calc (not frequent) or Writer (used regularly). I’m not sure if it only happens when I am editing Base forms, reports, etc… the crashing has slowed my progress into using Base for routine work! (They also happened, as described below, using Open Office/HSQL. I’ve always (mostly) used the embedded database engines.)
After one of the crashes of which I speak, the next time you launch one of the LO apps, you’ll probably get the “LO has crashed…” dialog. So far, touch wood, the “recovering previous session” process has always “worked”, although recent work on things (since the last SUCCESSFUL “save”) may have been lost.
I stressed “successful” because…
I THINK the seeds of disaster are somehow sown during the save process. Even though the machine freeze-up occurs later… a nasty little “gotcha”. Another suspect for the cause of the crash is using the very convenient facility that LO offers that allows you to go back and forth between the design and run modes for things like forms and reports. When I always CLOSE something and then re-open it in the other mode when I want to go between modes, I seem to get the crashes less often.
Has anyone been near these circumstances? Have any further ideas for staying away from the crashes, even imperfect ideas, not guaranteed, like the one I set out in the previous paragraph? (In some sorts of work, these crashes can happen very frequently for me… to the extent that I start closing all open LO documents, restarting them BEFORE crashes, to see if the last “save” actually worked. These crashes are pretty damaging to getting anything done.)