Download it now!
Bug 126500 - High CPU utilization after stretching a table embedded in a table in Writer
Summary: High CPU utilization after stretching a table embedded in a table in Writer
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.2.5.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Writer-Tables-Nested
  Show dependency treegraph
 
Reported: 2019-07-22 08:47 UTC by hydro-test
Modified: 2020-02-25 02:49 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description hydro-test 2019-07-22 08:47:20 UTC
Description:
Writer loads the CPU heavily and the application becomes unresponsive after stretching a table (writing text) inserted into another table in Writer before two pages.

Steps to Reproduce:
1. Create a new document in Writer
2. Insert table (can be in 1 column)
3. Insert one more table into one of the cells of the existing table (it is possible in 1 column)
4. Enter text into the nested table so that it stretches over two pages


Actual Results:
The soffice.bin process starts loading the CPU heavily, and the application becomes non-responsive.

Expected Results:
Not like now.


Reproducible: Always


User Profile Reset: No



Additional Info:
Версия: 6.2.5.2 (x86)
ID сборки: 1ec314fa52f458adc18c4f025c545a4e8b22c159
Потоков ЦП: 4; ОС:Windows 6.1; Отрисовка ИП: по умолчанию; VCL: win; 
Локаль: ru-RU (ru_RU); Язык UI: ru-RU
Calc: threaded
Comment 1 Roman Kuznetsov 2019-07-23 09:45:18 UTC
can't repro in

Version: 6.4.0.0.alpha0+ (x86)
Build ID: c738be4de6886a0c96b7d10df7e78c8b2964c135
CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; 
Locale: ru-RU (ru_RU); UI-Language: en-US
Calc: threaded
Comment 2 Dieter 2019-07-24 10:24:08 UTC
I also can't confirm with

Version: 6.2.5.2 (x64)
Build-ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159
CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; VCL: win; 
Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE
Calc: threaded

and also not with

Version: 6.4.0.0.alpha0+ (x64)
Build ID: 8f98a7c4e5b1f0b249c026577805a378b8a533d5
CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2019-07-23_00:30:19
Locale: de-DE (de_DE); UI-Language: en-US
Calc: threaded

Please attach a sample document (with nested table after step 3), as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it)
Comment 3 QA Administrators 2020-01-25 03:31:46 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2020-02-25 02:49:30 UTC
Dear hydro-test,

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