Bug 84322

Summary: Exiting LibreOffice crashes showing "The memory could not be "read"" error
Product: LibreOffice Reporter: Kevin Suo <suokunlong>
Component: SpreadsheetAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED WORKSFORME QA Contact:
Severity: minor    
Priority: medium CC: mariosv, mst.fdo, serval2412, suokunlong
Version: 4.2.3.1 rc   
Hardware: x86 (IA32)   
OS: Windows (All)   
See Also: https://bugs.freedesktop.org/show_bug.cgi?id=81468
https://bugs.freedesktop.org/show_bug.cgi?id=70154
Whiteboard:
i915 platform: i915 features:

Description Kevin Suo 2014-09-25 09:50:04 UTC
When open Calc, click "file" menu, move down some items and then exit, LibreOffice will show "The memory could not be "read"" message.

Steps to reproduce:
1. New Calc
2. Click on "File" menu, and move your mouse down to "New".
3. Exit Calc.

Current behaviour:

The error message pops up:
The instruction at "0x00000000" referenced memory at "0x7c931980". The memory could not be "read"....

Expected: No error message when exit.

OS: Windows XP SP3 X86
Version: 4.3.2.1
Build ID: f9b3ad49d92181b0a1fe7e76f785a2c2cd0847d3
Comment 1 Kevin Suo 2014-09-25 10:02:38 UTC
If you could not reproduce, please try some more times. For me I reproduce 9 times in 10.
Comment 2 m.a.riosv 2014-09-25 21:59:33 UTC
Hi Kevin, have you tried resetting user profile?

https://wiki.documentfoundation.org/UserProfile
Comment 3 Julien Nabet 2014-10-06 16:29:19 UTC
Following mariosv's comment, put it NEEDINFO.
Comment 4 Kevin Suo 2014-10-17 09:57:29 UTC
(In reply to m.a.riosv from comment #2)
> Hi Kevin, have you tried resetting user profile?

Yes I did. It was a fresh profile.
Comment 5 Julien Nabet 2014-10-19 07:59:43 UTC
Considering the fact that the bugs in cc of this one are quite similar, I think there's a real problem here.
Would it be possible you retrieve a backtrace by following this link?
https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace
Comment 6 Michael Stahl 2014-10-24 12:54:15 UTC
i can't reproduce the crash with current master
Comment 7 Doctor Donut 2014-11-18 21:05:25 UTC
CoE thoughts
my system: Windows XP SP3, never crashes, no virus protection, totally clean

LO rarely crashes, except in this instance almost always:

+ LO is not running
+ double-click any text or spreadsheet or CSV document via any file explorer
+ do some work on opened file or not
+ click on right top [X] or on [File], [Exit] and get the memory crash

I spent hours trying all kinds of things to prevent this but the only (most of the time) is:
+ before I close LO I close the document
+ I click once or twice in a blank area of the application list / menu on the green left side of the screen
+ I wait about a second
+ then I close via the [X] or [File], [Exit] and LO quits without the crash

I have used this technique for weeks with very few problems
Comment 8 Julien Nabet 2014-11-18 21:08:24 UTC
(In reply to Doctor Donut from comment #7)
> CoE thoughts
> my system: Windows XP SP3, never crashes, no virus protection, totally clean
With which LO version?
(Last stable one is now 4.3.4)
Comment 9 Kevin Suo 2014-11-19 02:26:34 UTC
(In reply to Julien Nabet from comment #5)
I don't use Windows XP anymore, so I am not able to test this issue any more.

@Doctor Donut: Maybe you can try to prepare a backtrace (if you can reproduce this issue with the latest 4.3.4 version)?
Comment 10 Doctor Donut 2014-11-19 03:25:25 UTC
LO 4.3.4
I should have tested this version and the previous one.
Before that I got memory crashes all the time on LO exit.
However, I just tried 4.3.4 a lot and I can't crash it.
Well, maybe I should have brought up my "circumvention" a year ago when the problem was happening a lot.

> With which LO version?
> (Last stable one is now 4.3.4)
Comment 11 Julien Nabet 2014-11-19 06:34:28 UTC
So let's put this one to WFM.
If someone can reproduce it with last stable LO version (4.3.4), please don't hesitate to reopen this tracker.

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.