Bug 142377 - [FILEOPEN DOC] not responding when importing doc
Summary: [FILEOPEN DOC] not responding when importing doc
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:doc
Depends on:
Blocks: DOC-Opening
  Show dependency tree / graph
 
Reported: 2021-05-19 14:12 UTC by dan.bellew
Modified: 2024-09-05 03:17 UTC (History)
0 users

See Also:
Crash report or crash signature:

Attachments
Example file (983.00 KB, application/msword)
2021-05-19 20:24 UTC, Telesto 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description dan.bellew 2021-05-19 14:12:29 UTC 
Description:
LibreOffice hangs when I open a ms doc. CPU goes to 100% and Ubuntu show a not responding warning.

Steps to Reproduce:
1. Open this doc in LO
https://meyda.education.gov.il/files/Rama/Test_Units/Eng_langH_5_Havanat_Easy_2015_T.doc

Actual Results:
LO hangs and CPU is on 100%.

Expected Results:
Doc should open.


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.1.3.2 / LibreOffice Community
Build ID: 12a8e3cbd24a3757385a302d290655d4f3c7ebf1
CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: gtk3
Locale: en-US (en_IL); UI: en-US
Calc: threaded
Comment 1 Telesto 2021-05-19 20:24:29 UTC 
Created attachment 172177 [details]
Example file
Comment 2 Telesto 2021-05-19 20:27:21 UTC 
Repro with
Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: d7f734db2c078ced3ce08ad58cd816a79abe3bcf
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL

4.4.7.2

4.0

3.0.0
Comment 3 Timur 2021-05-20 13:12:03 UTC 
Repro for DOC, not for DOCX saved in MSO.
No repro if in MSO removed header or body.
Comment 4 QA Administrators 2024-09-05 03:17:29 UTC 
Dear dan.bellew,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug