Bug 121533 - Crash in: StrCmpICW
Summary: Crash in: StrCmpICW
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.1.0.3 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-19 22:21 UTC by Al McAusland
Modified: 2019-06-29 02:59 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: ["StrCmpICW"]


Attachments
Sample document as requested (807.58 KB, application/vnd.oasis.opendocument.text)
2018-11-21 18:59 UTC, Al McAusland
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Al McAusland 2018-11-19 22:21:31 UTC
This bug was filed from the crash reporting server and is br-ef57146d-f9aa-42bd-86fc-baef4be6c45c.
=========================================
I was running LibreOffice with 4 separate windows - 2 x Writer and 2 x Calc. Originally, I was working mainly in one of the Writer windows when it became unresponsive, and I killed the LibreOffice process tree and restarted LibreOffice. The restart successfully presented the document recovery process and no document information had been lost.

I had cause to repeat the above sequence of actions about 4 times.

One one of these restarts (the 3rd, I think), with the 4 document windows recovered, I was again working in the same Writer window as previously when Libreoffice simply crashed with no warning.

The Writer document I was working on was one landscape A4 page, contained one jpeg image, about 160 callouts (created using the Drawing toolbar), and a handful of Text boxes (again created using the Drawing toolbar).

I have worked on this document with previous versions of LibreOffice with no real issues.

My apologies that I cannot provide more precise information than this on the nature of the crash, but I hope this info may be of some use.
Comment 1 Xisco Faulí 2018-11-19 22:47:04 UTC
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)

I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
Comment 2 Al McAusland 2018-11-21 18:59:16 UTC
Created attachment 146890 [details]
Sample document as requested

As requested, I have attached a copy of the document which I was editing at the time of the crash. Any personally identifiable content has been substituted and meta information has been removed.
Comment 3 Xisco Faulí 2018-11-29 10:40:08 UTC
Hello Al McAusland,
Thanks for providing the document.
So the document opens fine for me. Any step I have to perform in order to reproduce the crash ?
Comment 4 Xisco Faulí 2018-11-29 10:40:23 UTC
OTOH,
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
Comment 5 QA Administrators 2019-05-29 02:53:30 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2019-06-29 02:59:13 UTC
Dear Al McAusland,

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-FollowUp