https://issues.apache.org/ooo/show_bug.cgi?id=125585
--- Comment #8 from [email protected] --- (In reply to oooforum from comment #7) > (In reply to oooforum from comment #5) > > I hope that I'm not being redundant here, but I'm having a similar issue, > > but without the message from Windows. > So this is not similar if it's different ;-) > > No news about the author since +30 days. > Like him, go to our support forum to get help. There is no help for these crashes in the forum, other than the already tried and not useful user profile replacement. I found a useful Windows 7 tool that keeps track of problems. It's the Reliability Monitor. It shows the list of O.O. crashes during the week when the reported problem happened. I am attaching a screen grab of the report, and the technical details of the soffice.bin crash I reported. As it can be seen on the crash report, it was a C++ Runtime error caused by the app. and pointing to the app. support team for information. To me this means that the OO team ought to investigate how soffice.bin interacts with the C++ library to terminate in an unusual way. I would think there aren't an infinite number of lines where soffice.bin calls C++ dll's to terminate. This would point to a way to a solution without having to reproduce the bug. My solution was simple: I uninstalled 4.1.1 and went back to 4.1.0. It still crashes a lot, but maybe between 2 and 5 times less often. Maybe someone will come up with a fix sometime. -- You are receiving this mail because: You are the assignee for the issue. You are watching all issue changes.
