https://bugs.documentfoundation.org/show_bug.cgi?id=154710
--- Comment #4 from Petr Neudek <[email protected]> --- For Stéphane Guillou (stragu) here is my forum post translated into English. Original https://forum.openoffice.cz/viewtopic.php?pid=25750#p25750 I have been experiencing a strange phenomenon for the past 4 days. I programmed a template for educational purposes on the topic of sorting algorithms. Everything was good in the beginning, but after a certain point I couldn't save the work. No error was visible in IDE Basic and I could test repeatedly. I just couldn't save the work. At that moment, LO stopped communicating. So I waited and when there was no change even after an hour, I had to turn off the LO. I tested everything possible. I reinstalled the installed version of LO 7.4.6 to 7.5.2 on two of my computers with W10. No luck - it behaved the same on both machines. I got around the problem by exporting Basic, which I immediately imported back after the crash. I was irritated by the information about the crash from the LO system: - "The Libre Office program is not responding. Please wait until the Windows system reports the problem to Microsoft". Also unusual behavior of LO after a crash, for example "lu5620ciyh3.tmp", which remain in the folder even after recovery. Now that I've come to terms with the fact that I'll be storing Basic externally. There was a message from Petr Valach that a new version of Apache OpenOffice 4.1.14 was released. I installed it and lo and behold. The macro immediately reported an error in the code. It was a code for a button in a cell where I would certainly not expect it: Dim oObjAnchor as object oShape.Size = oSize oDrawPage.add(oShape) oObjAnchor = oShape.Anchor with oShape .Anchor = oObjAnchor.getCellByPosition(17,5) end with LO didn't report any error and the button worked fine - just couldn't save it. I solved the problem easily. I used a hyperlink instead of the button that started the replay of the demonstration and the problem was solved. But such a tricky mistake must be solved. The error is that LO does not detect its own error and sleeps after the save command. I've experienced something similar before. Specifically, an error in "generalFunction.COUNT". I rewrote various macros for half a year and when I was done with the corrections, the LO correction came - nothing but a big waste of time and nerves. -- You are receiving this mail because: You are the assignee for the bug.
