With LO 4.4 and 4.4.1 I've started seeing "unknown software exception 0x40000015 at address 0x0036327c" error quite often. It happens when I close manually the quickstart app or when I close Writer. I've tried recreating the profile, uninstalling etc. but the issue is reoccurring. It did not happen with 4.3.6. I[m using Win XP SP3.
Does it go away if you repair the LibreOffice install and deselect Quickstart? Also, to you by chance have an instance of Apache OpenOffice installed?
No AOO on this machine. It was reformatted about one year ago, since then only LO. Still getting the error (and sometimes the other one). This is what I did and the results: 1. Removed LO 4.4.1 2. Installed LO 4.3.6 3. Installed LO 4.4.1 without quickstarter. 4. Got the error as described above. 5. Run "repair" function. 6. Still getting the error. 7. I'm getting "DDE Server Widnow: soffice.bin" error: "unknown software exception 0x40000015 a address 0x0036327c" every time I close Calc (open - close - get the error message). 8. I'm also getting the same error for every other LO module but only after I enter options (tools - options) and then close the program. Doesn't matter if I make any changes or whether I hit OK or cancel. As a side note I also got another error message but only a couple of times. Not sure if this is related or not: "The instruction at "0x7c911689" referenced memory at "0xffffffff". The memory could not be "read". That one appeared briefly after the installation and went away after repair. I think it starter when I deselected "Allow use of OpenCL" but I was not able to recreate it.
Created attachment 113944 [details] WinDbg backtrace Reproducible on master: Version: 4.5.0.0.alpha0+ Build ID: 797c48f0f74501def9f47444538c0e110fcfcca1 TinderBox: Win-x86@39, Branch:master, Time: 2015-03-01_04:01:32 Locale: lt_LT Open any ods document, copy some cells, close Calc.
*** Bug 89764 has been marked as a duplicate of this bug. ***
Additional info added as requested. Setting to Unconfirmed as instructed.
*** Bug 90944 has been marked as a duplicate of this bug. ***
Confirmed in comment 3, setting as new
I confirm the bug : Windows XP SP3, LO 4.4.5 just installed. Open a XLS file, close LO : crash. DDE server windows : soffice.bin application error : the instruction at 0x7c920a19 referenced memory at 0xffffffff. The memmory could not be read. I can give you sample file and other useful data, please let me know what to do. Best regards,Sala
Windows 7 SP1 : same file as my previous comment : LO 4.3.6 open and close ok, LO 4.4.5 ok.
@Massimo Sala, Not helpful. Version -- the oldest build issue is produced on, not the most recent. Resetting version back to 4.4.1.2 as reported by OP, if it exists further back set that. Otherwise please do not change. Additional WinDbg trace and exception analysis with symbols from Windwows XP sp3 users would be helpful.
Created attachment 118819 [details] windbg log > Resetting version back to 4.4.1.2 as reported by OP, if it exists further > back set that. Otherwise please do not change. Ok, sorry. > Additional WinDbg trace and exception analysis with symbols from Windwows XP > sp3 users would be helpful. windbg : I atttach to LO, with the file open. Close LO, fine. So from windbg I relaunch LO, and now closing it faults. Please see if the attached log is useful. environment : Win XP SP3 italian Massimo
Created attachment 118820 [details] procmon, case ok I also attach two sysinternals procmon logs ( two different execution, not related to the previous windbg test ). environment : Win XP SP3 italian Massimo
Created attachment 118821 [details] procmon, crash on exit the crash is at step 471
I forgot. Closing the XLS document not always crashes LO. Windows XP SP3 with Microsoft EMET 4.1.1 and Kaspersky Endpoint Security 10 : about 5 crashes every 20. Windows XP SP3 without EMET without KES : about 3 crashes every 20. Windows sees 2.96 GB of total RAM available.
Any news ? Is there anybody working on this ?
Any news ? Is there any willing to fix this ?
Created attachment 119141 [details] windbg call stack of GetSloarMutex hang on 4.4.3.1 No longer able to reproduce on XP sp3 32-bit en-US with Version: 4.4.5.2 (wef 2015-07-22) Build ID: a22f674fd25a3b6f45bdebf25400ed2adff0ff99 Locale: en_US But on Windows XP sp3 32-bit en-US with Version: 4.4.3.1 (wef 2015-04-14) Build ID: b2f347f2ac68821efc00b6f1793cda90af748118 Locale: en_US In a WinDbg session closing LibreOffice, with cells copied from a Calc session. Hangs in WinDbg as below... A ~* call stack of the hung process attached... 0:000> g (a44.9a0): Access violation - code c0000005 (first chance) First chance exceptions are reported before any exception handling. This exception may be expected and handled. eax=00000000 ebx=00000000 ecx=00e3fc74 edx=7c90e514 esi=00e3fc74 edi=12cdf764 eip=02c0eee5 esp=00e3fc5c ebp=00e3fc84 iopl=0 nv up ei pl nz na pe nc cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010206 vcllo!Application::GetSolarMutex+0x5: 02c0eee5 8b4804 mov ecx,dword ptr [eax+4] ds:0023:00000004=???????? 0:000> g (a44.9a0): Access violation - code c0000005 (!!! second chance !!!) eax=00000000 ebx=00000000 ecx=00e3fc74 edx=7c90e514 esi=00e3fc74 edi=12cdf764 eip=02c0eee5 esp=00e3fc5c ebp=00e3fc84 iopl=0 nv up ei pl nz na pe nc cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000206 vcllo!Application::GetSolarMutex+0x5: 02c0eee5 8b4804 mov ecx,dword ptr [eax+4] ds:0023:00000004=????????
(In reply to V Stuart Foote from comment #17) Oops, spoke too soon, much less often, ~10%, but still crashing in 4.4.5.2 with same STR and error as with 4.4.3.1 (which was 99% crash). @Michael S., looking at the trace, it seems to be some of the same area of SolarMutexGuard you worked on for master with https://gerrit.libreoffice.org/#/c/16515/ , is there any hope for Windows XP users?
Created attachment 119143 [details] windbg call stack of error hang on 4.4.5.2 Poking at this a bit more... Windows XP sp3 32-bit en-US with Version: 4.4.5.2 Build ID: a22f674fd25a3b6f45bdebf25400ed2adff0ff99 Locale: en_US With 4.4.5.2, get a clean shutdown 9 of 10 times. ~10% hang. Attached another set of call stacks for the 4.4.5.2 crashes--when able to catch them. Seems a bit different than the 4.4.3.1 crash. Also, after detaching debugger the error reads: DDE Server Window: soffice.bin - Application Error The instructions at "0x7c910a19" referenced memory at "0x00000000". The memory could not be "read". So not so sure this is still the same issue, but it seems to still be memory related on 32-bit XP. using a WinDbg - Symbols path of: CACHE*C:\symbols;SRV*http://dev-builds.libreoffice.org/daily/master/Win-x86@39/symbols;SRV*http://dev-downloads.libreoffice.org/symstore/symbols;SRV*http://msdl.microsoft.com/download/symbols
hi every one. i confirm the error message occured most of times in my system, windows xp, proffessional, service pack 3, en-us. DDE Server Window: soffice.bin - Application Error The instructions at "0x7c910a19" referenced memory at "0x00000000". The memory could not be "read". please okay to terminate the program! no different which type of document i want to use, no different i want to use persian or english document. when i want to open a document, read it or edit it, after my work i press alt f4 to close the program, i recieved this message. i tested many versions between libreoffice version 4.3.0.4 and even 4.4.6.3, installed and portable versions. in all of them, the error mesage and the libreoffice writer when closing the document, was the same! as i know, only writer is accessible currently and i only use writer. but when i installed version 5.0.2.1 of libreoffice the error message that i mentioned, is very rarely in compare to versions 4.3 and 4.4.
Migrating Whiteboard tags to Keywords: (regression)
hello. i tested version 5.0.3.1 in my daily works and editing my documents. the errors that mentioned in this bug is not completely solved for me and i see it. but less time when i compare it with versions 4.3. and 4.4 i did not knew about locale and now i tested in both en-us and also always my locale is fa-ir i think that i use version 4.3.7 in a near future again.
hello. i tested version 5.0.3.1 in my daily works and editing my documents. the errors that mentioned in this bug is not completely solved for me and i see it. but less time when i compare it with versions 4.3. and 4.4 i did not knew about locale and now i tested in both en-us and also always my locale is fa-ir i think that i use version 4.3.7 in a near future again.hi again. i tested version 5.0.3.1 and wanted to edit my documents. i think these two error messages that you mentioned in this bug is for using memory in windows xp. i did not knew about locale and now i tested in both en-us and fa-ir locale. but my locale is always fa-ir and i saw this error messages in all versions of libreoffice that i tested until now. error messages in libreoffice 4.3 and 4.4 happened many many times and in libreoffice 5.0 the percentage of recieving this errors for me reduced but not completely solved until now. i think that in the very near future i back to version 4.3.7.2 but i recieve error message about microsoft visual c runtime library runtime error thats a very big issue for me.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
All is fine now, bug is gone.
(In reply to QA Administrators from comment #24) > ** Please read this message in its entirety before responding ** > > To make sure we're focusing on the bugs that affect our users today, > LibreOffice QA is asking bug reporters and confirmers to retest open, > confirmed bugs which have not been touched for over a year. > > There have been thousands of bug fixes and commits since anyone checked on > this bug report. During that time, it's possible that the bug has been > fixed, or the details of the problem have changed. We'd really appreciate > your help in getting confirmation that the bug is still present. > > If you have time, please do the following: > > Test to see if the bug is still present with the latest version of > LibreOffice from https://www.libreoffice.org/download/ > > If the bug is present, please leave a comment that includes the information > from Help - About LibreOffice. > > If the bug is NOT present, please set the bug's Status field to > RESOLVED-WORKSFORME and leave a comment that includes the information from > Help - About LibreOffice. > > Please DO NOT > > Update the version field > Reply via email (please reply directly on the bug tracker) > Set the bug's Status field to RESOLVED - FIXED (this status has a particular > meaning that is not > appropriate in this case) > > > If you want to do more to help you can test to see if your issue is a > REGRESSION. To do so: > 1. Download and install oldest version of LibreOffice (usually 3.3 unless > your bug pertains to a feature added after 3.3) from > http://downloadarchive.documentfoundation.org/libreoffice/old/ > > 2. Test your bug > 3. Leave a comment with your results. > 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; > 4b. If the bug was not present in 3.3 - add 'regression' to keyword > > > Feel free to come ask questions or to say hello in our QA chat: > https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa > > Thank you for helping us make LibreOffice even better for everyone! > > Warm Regards, > QA Team > > MassPing-UntouchedBug hello, sorry for my late response. i had many issues using libreoffice and sometimes i missed or forgot the bug number to reply fast! the error about: DDE server windows : soffice.bin application error : the instruction at 0x7c920a19 referenced memory at 0xffffffff. The memmory could not be read. or any other similar error memory in using libreoffice on windows xp 32bit sp3 which i have, are completely resolved for me since testing version 5.2.5.1 or even maybe in 5.2.0! thanks so much for providing free office program for us, God bless you all and his infinite mercy i pray for you!