Bug 105878 - Using "undo changes" functions, crash in: BigPtrArray::operator[](unsigned long)
Summary: Using "undo changes" functions, crash in: BigPtrArray::operator[](unsigned long)
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.2.0.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-09 12:10 UTC by brodders
Modified: 2017-09-29 08:55 UTC (History)
2 users (show)

See Also:
Crash report or crash signature: ["BigPtrArray::operator[](unsigned long)"]


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description brodders 2017-02-09 12:10:02 UTC
This bug was filed from the crash reporting server and is br-5e3e0345-7556-4d42-a005-eff39619da34.
=========================================

Activity:

Written large doc with images and text in LibreOffice .odt format.

Older version was in Word .docx format.

Opened Edit > Track Changes > Compare Document

and entered the Word doc details. Loaded and performed compare OK.

However this new documents (showing changes) was with my "live" filename, which I did not want to have the changes shown on.

Used Ctrl-Z and Crash.


As this is a paper due to be handed in soon, I am not going to repeat the experiment - not can I attach them due to confidentiality issues.
Comment 1 Xisco Faulí 2017-02-09 12:20:19 UTC Comment hidden (obsolete)
Comment 2 V Stuart Foote 2017-02-09 14:17:53 UTC
Looking at Crash report, OP was on 5.3.0.3 but the issue present from the 5.2.0.4 builds (just 39 instances so not prevalent). Need a good set of STR and a sample document that causes the crash.

My simple testing of a few minor changes, with <Ctr>+Z reversion is not enough to trigger.
Comment 3 QA Administrators 2017-08-30 19:28:01 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2017-09-29 08:55:07 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA 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 our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20170929