Bug 65150

Summary: FILESAVE: Crash on exit after editing and saving spreadsheet
Product: LibreOffice Reporter: bb120190
Component: SpreadsheetAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: medium CC: barta, bfo.bugmail, serval2412
Version: 3.6.5.2 release   
Hardware: Other   
OS: Windows (All)   
See Also: https://bugs.freedesktop.org/show_bug.cgi?id=81468
Whiteboard: BSA
i915 platform: i915 features:

Description bb120190 2013-05-30 00:49:52 UTC
This is going to sound silly, but I need to narrow this down somehow, so please help! I'm running Windows XP 2002 SP3.

Problem description: 

Steps to reproduce:
1. Run Calc
2. Save blank spreadsheet to disk
3. Quit Calc
4. Reopen saved blank spreadsheet
5. Click a random cell and mash the keyboard followed by ENTER
6. Save
7. Quit Calc: it crashes (see below)
8. Reopen saved spreadsheet: Calc crashes with an unhandled Win32 exception.

ERROR BOX FOR STEP 7:
---------------------------
DDE Server Window: soffice.bin - Application Error
---------------------------
The instruction at "0x10006a1f" referenced memory at "0x9004630c". The memory could not be "read".


Click on OK to terminate the program
---------------------------
OK   
---------------------------
Operating System: Windows XP
Version: 3.6.5.2 release
Comment 1 Julien Nabet 2013-05-31 22:47:10 UTC
Do you reproduce this with newer version 4.0.3?
Comment 2 bb120190 2013-05-31 23:00:47 UTC
Yes, tried on 4.01 and 4.03 too. Same results.





On Fri, May 31, 2013, at 11:47 PM, [1]bugzilla-daemon@freedesktop.org
wrote:

[2]Julien Nabet changed [3]bug 65150



       What
                  Removed
                                  Added
  Status
                UNCONFIRMED
                           NEEDINFO
  CC
                           serval2412@yahoo.fr
  Ever confirmed
                           1

[4]Comment # 1 on [5]bug 65150 from [6]Julien Nabet
Do you reproduce this with newer version 4.0.3?
  __________________________________________________________________

You are receiving this mail because:

  * You reported the bug.

References

1. mailto:bugzilla-daemon@freedesktop.org
2. mailto:serval2412@yahoo.fr
3. https://bugs.freedesktop.org/show_bug.cgi?id=65150
4. https://bugs.freedesktop.org/show_bug.cgi?id=65150#c1
5. https://bugs.freedesktop.org/show_bug.cgi?id=65150
6. mailto:serval2412@yahoo.fr
Comment 3 Julien Nabet 2013-06-04 20:41:45 UTC
bb120190: please, could you answer from bugzilla link https://bugs.freedesktop.org/show_bug.cgi?id=65150# and not from your emailer.
Could you give a try after having renamed your LO directory profile? (see https://wiki.documentfoundation.org/UserProfile)
Comment 4 bb120190 2013-06-04 22:11:08 UTC
I did already try this - I renamed the profile directory and went through the same steps to test. A new profile directory was created after the first Calc start, but the crash behaviour was just as before.
Comment 5 Julien Nabet 2013-06-05 20:48:15 UTC
Thank you bb120190 for your feedback. I put back to "Unconfirmed" since I don't have more questions.
Comment 6 bb120190 2013-06-06 12:41:47 UTC
No problem. Is there a next step for this issue at present?
Comment 7 Tom Williams 2013-06-15 17:30:46 UTC
What do you mean by "mast the keyboard"?  Do you mean type some random letters or literally press on a bunch of keys at the same time?  Also, about how many characters appear for you when you "mash the keyboard"?

I've tried this in Calc 4.0.3.3 on Windows XP Home Edition (SP3) and couldn't get it to crash at all.

Thanks!

Peace...
Comment 8 bfoman 2013-06-25 09:54:11 UTC
Please try to deliver a backtrace following https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg article.
Comment 9 tommy27 2014-05-04 00:15:03 UTC
are you still experiencing issue with current LibO 4.1.6 or 4.2.3 final releases?
moreover would you please define what you mean "mash the keyboard"?
Comment 10 Julien Nabet 2014-05-27 20:34:21 UTC
No feedback since months, put it at WFM.

bb120190: if you can reproduce this with a recent LO version (4.2.4 or at least 4.1.6), please provide a backtrace following this link:
https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg
Comment 11 bb120190 2014-07-18 09:42:34 UTC
I was eventually forced to conclude that this was down to a subtly degraded Windows-XP build. I've since rebuilt the machine in question with Win7 and haven't seen the problem since.

Feel free to close this.

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.