Bug 127375 - Can't work with the document, the application is not responding
Summary: Can't work with the document, the application is not responding
Status: VERIFIED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.0.7.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Memory
  Show dependency tree / graph
 
Reported: 2019-09-05 13:45 UTC by Vera Blagoveschenskaya
Modified: 2019-09-11 16:30 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
test document (314.64 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2019-09-05 13:45 UTC, Vera Blagoveschenskaya 		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 Vera Blagoveschenskaya 2019-09-05 13:45:08 UTC 
Description:
Can't work with the document, the application is not responding

Steps to Reproduce:
1. Try to open file from the attachment

Actual Results:
Can't work with the document, the application is not responding

Expected Results:
Normal work


Reproducible: Always


User Profile Reset: No



Additional Info:
Reproduced for 
Version: 6.2.5.0.0+
Build ID: 23ccf16e9e86ecc64367f41f4df695d0a6926d72
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: kde5; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:libreoffice-6-2, Time: 2019-05-21_15:11:03
Locale: ru-RU (ru_RU.UTF-8); UI-Language: en-US
Calc: threaded

NOT reproduced for
Version: 6.3.0.0.alpha1+
Build ID: 77ae0abe21f672cf4b7d2e069f1d40d20edc49a7
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: kde5; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-05-31_15:33:33
Locale: ru-RU (ru_RU.UTF-8); UI-Language: en-US
Calc: threaded

NOT reproduced for
Version: 6.3.0.0.alpha1+
Build ID: 77ae0abe21f672cf4b7d2e069f1d40d20edc49a7
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: kde5; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-05-31_15:33:33
Locale: ru-RU (ru_RU.UTF-8); UI-Language: en-US
Calc: threaded
Comment 1 Vera Blagoveschenskaya 2019-09-05 13:45:42 UTC 
Created attachment 153921 [details]
test document
Comment 2 Vera Blagoveschenskaya 2019-09-05 13:47:57 UTC 
NOT reproduced for
Version: 6.4.0.0.alpha0+
Build ID: 1496a1831d1be0a2d24be9fe3ecf627b2664e938
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: kf5; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-09-04_14:52:26
Locale: ru-RU (ru_RU.UTF-8); UI-Language: en-US
Calc: threaded
Comment 3 Oliver Brinzing 2019-09-05 18:03:39 UTC 
confirming with:

Version: 6.0.7.3 (x64)
Build-ID: dc89aa7a9eabfd848af146d5086077aeed2ae4a5
CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; 
Gebietsschema: de-DE (de_DE); Calc: 

cpu at 25% (one core) and memory consumption increases steadily.
looks like a memory leak
Comment 4 Vera Blagoveschenskaya 2019-09-06 14:35:33 UTC 
Additional research:
I've checked this memory leak more carefully and found out that the problem is not reproduced for Build ID: 23ccf16e9e86ecc64367f41f4df695d0a6926d72.

Probably the reason is in 'downstream' build.

Set the status -> WFM.
Comment 5 Oliver Brinzing 2019-09-06 18:16:44 UTC 
(In reply to Vera Blagoveschenskaya from comment #4)
> Additional research:
> I've checked this memory leak more carefully and found out that the problem
> is not reproduced for Build ID: 23ccf16e9e86ecc64367f41f4df695d0a6926d72.

yes, not reproducible with:

Version: 6.4.0.0.alpha0+ (x64)
Build ID: 27c886f5aa8e53b22caf0ef9d721f60e77cd65f2
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
Locale: de-DE (de_DE); UI-Language: en-US
Calc: threaded
Comment 6 Vera Blagoveschenskaya 2019-09-11 13:56:38 UTC 
Verified due to Comment 4 and Comment 5