Created attachment 79288 [details] LO Writer crashes after opening this file After opening DOC (see attachment) file LO crashes. It happens onn all Windows platforms. But there is no problem opening and working with this file under Linux (AMD64)
I can confirm the crash on OS X 10.8.3 with LO 4.0.3.3. I get a hang and have to kill LO. Thus setting to NEW.
Created attachment 79299 [details] Bug 64578 - WinDbg session with FAILED_SOURCE_CODE Confirmed with: LO 4.0.2.2 Build ID: own W7 debug build Windows 7 Professional SP1 64 bit Attached full WinDbg session with mini dump file loaded generated by procdump soffice.bin -h.
Comment on attachment 79288 [details] LO Writer crashes after opening this file Mimetype fixed
On pc Debian x86-64 with master sources updated today, I don't reproduce the crash. However, I noticed this on console: warn:legacy.osl:20744:1:sot/source/sdstor/stgdir.cxx:419: Trying to resize readonly stream by seeking, could be a wrong offset! Michael: mutex problem partly solved or fdo#46808 (convert Uno services) may have helped on master? Or not reproduceable on Linux? Other?
Works for me too in 4.0.3+ which is annoying; bfoman's trace is great - but it seems to point to something that I find hard to believe to be the problem - looks like it's related to grammar checking. Is it possible that we need to as Windbg to print a trace for all threads ? Can we get a better trace ?
On Win7 with 4.0.3.3 and a brand new LO profile, I don't reproduce the crash but it hangs. (I waited for about 30 secs)
q12w / bfoman - when you say crash; do you mean a long hang ? :-) [ as in it may take a long time to load ? ]. If so - we should still fix the long hang of course; bfoman - I see you did interrupt it in what is prolly this long hang; the thread you interrupted is not the slow one doing the work (I think). Any chance of a trace of all threads' status at that point ? I'd expect the grammar checker to be mis-behaving in some expensive way :-) Thanks !
(In reply to comment #7) > not the slow one doing the work (I think). Any chance of a trace of all > threads' status at that point ? I'd expect the grammar checker to be > mis-behaving in some expensive way :-) I will revisit this bug report. Any additional WinDbg commands to be typed are welcomed...
bfoman: perhaps this page may help http://www.windbg.info/doc/1-common-cmds.html, above all this part " !uniqstack : show stacks for all threads " ?
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of FDO
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.