https://bz.apache.org/ooo/show_bug.cgi?id=128591
--- Comment #2 from [email protected] --- (In reply to sundialservices from comment #1) > I agree that it is probably the same issue. (Problem #128535.) > > The real problem here is that OpenOffice allows an exception to percolate > all the way to the top – to the operating system, which responds by killing > the entire process. No matter what actually happens during the "automatic > update" process, OO should "try" it, and "catch" anything that goes wrong. > Right now it doesn't. Access to invalid memory doesn't cause a friendly "exception", it is the SIGSEGV signal, recovery from which is possible but very difficult (signal handlers, custom stacks, changing CPU registers, machine code), and can still leak memory or compromise security. A better solution is to prevent the incorrect memory access in the first place. -- You are receiving this mail because: You are the assignee for the issue.
