https://bugs.documentfoundation.org/show_bug.cgi?id=89127
--- Comment #4 from RickWriter <[email protected]> --- Applying some of the suggestions recommended has lead me to feel the problem focuses on lock files placed when a crash occurs. Here is a rough sequence of events: 1-I created a macro that ended up unresponsive after I experimented with debugging tools. I stopped the macro by terminating LibreOffice via the Windows Task Manager. It would appear that this set a ~lock file on LO or some portion of it. 2-Upon restarting the program, things seemed normal until I again started to experiment with my macro. Every time I opened the macro organizer the program froze. 3-Following information obtained on various websites, updated Java as well as LibreOffice, to no avail. 4-I filed the bug report. 5-In response to comments, I refined my Google search, changed hidden files to visible, changed the name of my LO profile so as to force LI to create a new one for me, sought out and deleted various lock files, and learned to terminate LO more gently by using the Windows Task Manager to stop Soffice processes rather than the LO application. 6-These steps have allowed me to work in LO once again. Thank you for your assistance. Cheers, Rick Lehtinen -- 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
