I work in .odt format but I always also save in .doc format, because my collaborators demand it. When I close Writer after I have finished an edit cycle and saved both formats I get 'DDE Server Window: soffice.bin - Application Error'. The latest example error text is: 'The instruction at "0x7c9109f9" referenced memory at "0xffffffff". The memory could not be "read", Click on OK to terminate the program'. I don't know if the .doc file is corrupted. I don't take a chance. I immediately open the .odt version and save it again as a .doc. It almost always saves and exits quietly when I do it this way. Me thinks a pointer variable is not properly initialized. Version: 4.4.6.3 Build ID: e8938fd3328e95dcf59dd64e7facd2c7d67c704d Locale: en_US, running in Windows XP Pro version 2002 SP3; running in Parallels Desktop 9 for Mac, Build 9.0.24251 (revision 1052177: Thursday, August 28, 2014; running in OS X, 10.8.5.
Hi @Will, thanks for reporting. I can't reproduce on Win10x67 with 4.4.7.2. Please try resetting the user profile, sometimes solves strange issues. https://wiki.documentfoundation.org/UserProfile If it doesn't works, since version 5.0 there is a new option for "Save a copy as", that could be of interest for you. Or you can be interested in the extension: http://extensions.libreoffice.org/extension-center/multisave-1
For the test, could you give a try to last stable LO version 5.0.3? If you still reproduce this, would it be possible you retrieve a backtrace (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace)?
I think the suggestion to verify/edit my LO profile was a good one. I discovered the path to .../temp was obsolete. I changed this to conform in pattern to the other profile variables and thus far, I have not been able (4x times) to cause the address error on closing Writer.
Thank you for your feedback, let's put this one to WFM then.
Not so fast. Fifth try was the charm. Opened the doco I have been editing, made no changes and simply closed Writer by poking the X close icon and got the same address error. I'll try the next suggestion, upgrading to a 5.0.* version, that is, if and only if 5.0 is available for 32-bit XP. I am not into upgrading whenever some new release comes along. If I did I'd spend all my time upgrading/installing new SW rather than getting real work done ;-)
Ok, let's put this one to UNCONFIRMED then since you responded to all the asked info.
I downloaded: Version: 5.0.3.2 Build ID: e5f16313668ac592c1bfb310f4390624e3dbfb75 Locale: en-US (en_US) and I'm banging away at it and so far so good, but let's hold off WFM until I give it a more thorough workout. And since I have your attention, one reason .doc and Word are absolutely indispensable is Word's superior grammar checker (in Office 2000). LO fails to find fine-grained grammar issues: for example, semicolon usage and subtle verb usage issues, such as was versus were. It seems to know nothing about mood or context, as in the difference between something that could happen and something that did happen and sometimes gets who versus whom wrong. When in doubt I always put my prose through Word's spell/grammar checker, than back to LO, since I won't upgrade Windows. Word occasionally gets things wrong too but much less frequently. What's the big deal, you might ask? I write fiction as Thomas Docheri, so it's not just about portability, such as being able to emit .pdf, but about productivity, and using the tools to help me be a better writer.
Please @Will " And since I have your attention," doesn't work here. One issue by bug report, is how works. If you want explain the asked info, fine, if not please close the bug or explain what you think can help to find the issue. OTOH, I guess you have set up properly the grammar checker? Menu/Tools/Options/Language Settings/English sentence checking.
Did not know grammar checker has options that can be tuned. Thanks. I'll compare with Word and hope for the best. Re the uninitialized address problem on close I reported, Version: 5.0.3.2 seems to have resolved it. I have tried to recreate the problem in this version and I cannot.