try upgrading to LibO 4.1.2.3 which was released just yesterday (by the way it's a recommended upgrade).

tell us if you still experience this bug or if this fixes the issue.

Hi Tommy, sorry for being late to answer, but unfortunately, even after installing version 4.1.2.3 (compilation ID 40b2d7fde7e8d2d7bc5a449dc65df4d08a7dd38) the crashes still occur.

I never experienced anyd data loss, only the crashes after (and only after) exiting Writer.

set status back to UNCONFIRMED

as an additional test try downloading the portbale version here:
http://sourceforge.net/projects/winpenpack/files/X-LibreOffice/releases/X-LibreOffice_4.1.2_rev16.zip/download

and tell us if it crashes the same way as the standard installation version.

Hi Tommy, I downloaded the portable version and, after editing some documents, it also crashed with the same message, just the instruction address changed from "0x01da65e3" to "0x01db65ed", i.e., the message can be translated from PT-BR as:

DDE Server Window: soffice.bin - Application error
The instruction at "0x01db65ed" referenced memory at "0x00000004". The memory could not be "read".

Maybe the crash trigger is the PDF export function?

Hi João Paulo,

Did you try to clean your LibreOffice user profile ?
https://wiki.documentfoundation.org/Faq/General/110


Best regards. JBF

Hi Jean, thank you for your suggestion, but when I used the portable version tommy27 suggested me, I was using a new user profile as the portable version use an internal folder for loading and saving user settings.

Even so, I tried with an empty user profile and the result was the same: a crash.

comment #6 answered to question in comment #5. So set status back to unconfirmed.

Best regards. JBF

*** Bug 73369 has been marked as a duplicate of this bug. ***

As stated in the other bug, this issue is related to the sidebar.

apparently this crash happens only on Windows, and for very few people.

it would probably be helpful if we had a backtrace of the crash.

https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg

Yes its limited to only Windows XP and it happens randomly. I would have like to send in a backtrace but couldnt get windbg installed on the OS and i tried to get it crash by opening it 10 or so times and it didnt crash once. It is quite strange this one.

(In reply to comment #11)
> apparently this crash happens only on Windows, and for very few people.
> 
> it would probably be helpful if we had a backtrace of the crash.
> 
> https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg

Sorry, I can't help with that. Migrated my both computers to Windows Vista and not using Windows XP anymore.

Still, I think this bug is related to the PDF Export function, but as Windows XP is still being used on many places (I hope places without Internet connection), you should weight if is worth to investigate and fix it.

very unlikely to be writer specific

May be the same issue as in bug 84322. Try if you can reproduce following my steps in https://bugs.freedesktop.org/show_bug.cgi?id=84322#c0

Hi, I am downloaded the WinDbg to try to get a backtrace (never did it before).

Followed the steps to try reproduce the crash (it only happened when used the PDF Export function), but had no success.

As I recall, after upgrading to version 4.2.6.3, build ID 3fd416d4c6db7d3204c17ce57a1d70f6e531ee21, never had the crash again.

Maybe the bug was fixed?

maybe has been fixed so let's mark this as RESOLVED WORKSFORME
feel free to revert status if you reproduce again

We've received a message from submitter of the duplicate bug 73369 that he still experiences this problem in 4.4.0.3, Windows XP SP3 (more instances).

The previously reported error window with the title "DDE Server Window: soffice.bin - Application error" appears when closing Writer or Calc.
The bug occurs unpredictably, only if the sidebar is shown and more frequently if the sidebar is expanded.

@Stanislav: If the submitter of bug 73369 can get a backtrace for the crash with windbg ( https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg ) and submit it here, the devs can look into finding out where the source of the problem seems to be.

Yes, I wrote him that this would be helpful (but I don't know how complicated getting backtrace on Windows is).

@Stanislav: I've personally rewrote the backtrace wiki and included screenshots of all the steps involved, so it should be very easy for him to get it done (you can give it a try to see how easy it is if you have windows). If he has any problems, please let me know.

Created attachment 113473 [details]
backtrace

I managed to reproduce this in WinXP (inside a VM). Attaching the backtrace. The bug can be consistently reproduced using Bohumír Džubej's reproduction steps in duplicate bug 73369 .

LibreOffice Portable v4.4.0.3 (English)

Windows XP Professional Service Pack 3

I have the same issue when using Writer.  After editing a document, saving it, and then clicking the Close windows button, I will see the following error:

**********

DDE Server Window: soffice.bin - Application Error

The instruction at "0x7c910a19" referenced memory at "0xffffffff". The memory could not be "read".

Click 'OK" to terminate the program

**********

Created attachment 113685 [details]
DDE Error Message

A screenshot of the DDE error message.

hi every one. 
yes. i confirm this bug in my system windows xp proffessional service pack 3. 
when i opened a document, read it, edit some point in it, or i wanted to close it without editing anything, and i pressed alt f4 to close the program i recieved this message exactly. 

DDE Server Window: soffice.bin - Application Error

The instruction at "0x7c910a19" referenced memory at "0xffffffff". The memory could not be "read".

Click 'OK" to terminate the program. 

its not different that which type of document i want to read or edit. 
in all of them, i recieved this message. 
in versions from version 4.3.04 and above until version 4.4.6.3 that are accessible for blinds without need to install java and java access briedge, i tested this subject with the same error message. 
and also i tested installed and portable versions of libreoffice between versions 4.3 and 4.4 with the same result! 
but when i installed libreoffice version 5.0.2.1, the error reduced fortunately and i recieved it very rarely. 
i can say even not more than 5 percent in the time of my using of libreoffice.

hi. 
i used libreoffice 5.0.2.1 for test and when i downloaded and installed version 5.0.3.1 and used it in my daily work and tried to edit my documents after closing libreoffice, the result was the same. 
i use windows xp professional service pack 3 and i tried in both fa-ir and also en-us locale. 
but in all versions that i used in my daily works and editing my documents, the result was the same and i am observing this error message in all versions. 

DDE Server Window: soffice.bin - Application Error

The instruction at "0x7c910a19" referenced memory at "0xffffffff". The memory could not be "read".

Click 'OK" to terminate the program

i think that i back to the version 4.3.7.2 in the near future and i think that this version was more simple and without need powerful hardware. 
but when i use versions of libreoffice before version 5, i faced a major error about microsoft visual c runtime library.

Any better with last stable LO version 5.1.3?

Can a dev look into the submitted backtrace (attachment 113473 [details]) and see if it sufficient to track down the problem.

Hi Aron; thanks for reproducing, and doing it with a symbols build. Unfortunately the trace is not so useful:

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE_SHUTDOWN_c0000005_memory_corruption!ntdll

It means that somewhere before this trace someone did something bad to the memory. However - if you have that VM setup, what would be really useful is running 'drmemory' on the binary:

That should make the app run -much- slower (20x at least), but it should also produce a big log that shows where this memory corruption occurs [ with stack traces ].

Do you think you could run it under drmemory ?

Thanks !

This regression was introduced before branch 4.4, thus it can't be bibisected with the current bibisect repositories. Changing keyword 'notBibisectable' to 'preBibisect'

(In reply to Yousuf Philips (jay) from comment #30)
> Can a dev look into the submitted backtrace (attachment 113473 [details])
> and see if it sufficient to track down the problem.

hi.
i tested libreoffice 5.1.4 and after exiting the result for me was crash.

hi.
i completely confirm that the issue still persist in libreoffice 5.0.5 and also 5.1.4 which i tested and even 5.0.6.
but in 5.0.6 for me is less than the other versions.

I set status to NEW since there have been multiple independent confirmations.
I also ask those people to tell if issue persists in latest LibO 5.2.3.3 release.

hi.
yesterday, i downloaded version 5.1.6.1 and 5.2.5.1
when i use 5.1.6 and maybe in all branches of 5.1, after exiting libreoffice writer via alt+f4 libreoffice becomes unresponsive and wants to report it to microsoft.
its not responsive famous bug which is appeares in many programs and even windows explorer!
and maybe this happen even using windows explorer because of using windows xp, but i am not sure completely.
and also i tested with 5.2 a little time and did not see such errors after exiting writer.
if i find new result for this, i comment it here.
with very little investigation, i think that all bugs related to exiting writer on windows xp is solved in 5.2 branche,
but as i mentioned i tested it little time and i report the changes if i face a new behaviour!
thanks so much for resolving bugs,
i pray for you in my five times daily prayers, request divine extreme mercy and blessings for you.

Zahra, I think that's a different issue to the one reported here.

Does this consistently occur for you? If so, please log a new bug report, and feel free to cc me in on it.

The DDE error can only really occur if Dynamic Data Exchange is being used, and if I had to hazard a guess we aren't closing the DDE link cleanly on exit.

The last version that supported Windows XP, 5.4, has reached EOL, therefore this ticket can now be closed as well.