Bug 103097 - Adding new row to a big ODT table causes procdump with 5.5+ (crash "No RTTI Data" before or with less memory)
Summary: Adding new row to a big ODT table causes procdump with 5.5+ (crash "No RTTI D...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Writer-Tables Memory Crash
  Show dependency treegraph
Reported: 2016-10-10 20:26 UTC by PeLe
Modified: 2022-06-13 03:26 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:
Regression By:

.odt file containing a big table with text and graphics (6.49 MB, application/vnd.oasis.opendocument.text)
2016-10-10 20:26 UTC, PeLe
Very sleepy stack (13.25 KB, application/vnd.oasis.opendocument.spreadsheet)
2020-06-12 15:20 UTC, Telesto

Note You need to log in before you can comment on or make changes to this bug.
Description PeLe 2016-10-10 20:26:05 UTC
Created attachment 127935 [details]
.odt file containing a big table with text and graphics

I am working with a growing table containing text and graphics.
First this crash occurred only after adding a lot of new rows without saving before closing. I learned to circumvent by saving every few minutes. Now the file is about 7 MB and the crash occurs by the mere "table/insert row" command.
Opening of the file takes more than 5 minutes.
Comment 1 MM 2016-10-16 20:39:56 UTC
Can't reproduce this one, coz it takes forever to load. Which is a bug as such.

On v5.1.5.2 under windows 7 x64 and ubuntu 16.04 x64 it opens with page 1 of 12 (and 100% zoom) and LO keeps on adding pages very slowly all the time.
With v5.2.2.2 and v5.3 under ubuntu 16.04 x64 it opens with page 1 of 270 (and 150% zoom) and hangs forever. Ended the program after 30 mins or so.
Comment 2 Buovjaga 2016-10-25 18:52:47 UTC
It opened for me properly as I left it alone for several minutes. I could insert a row, CPU went hard for a while, but no crash. I think it could be crashing for PeLe because he is running out of memory.

Arch Linux 64-bit, KDE Plasma 5
Build ID: cd7b306e614a938b7b39a66784899c22ee6f6c64
CPU Threads: 8; OS Version: Linux 4.8; UI Render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on October 25th 2016
Comment 3 Telesto 2017-06-09 15:42:35 UTC
No repro with
Build ID: 74d9b711d71cbaf4f853559211f6525db4a4b5db
CPU threads: 4; OS: Windows 6.19; UI render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2017-06-08_02:48:15
Locale: nl-NL (nl_NL); Calc: CL

File=opening is fast and I have no issue adding new table rows.
Comment 4 Timur 2017-06-09 16:34:34 UTC
With a trick of procdump, I notice that previously there was dump on fileopen, which is not present now with libo-master~2017-06-09_02.15.11_LibreOfficeDev_5.5.0.0.alpha0_Win_x86. And opening is faster, 270 pages, scrolling acceptable for me. 

What's not ok is procdump on insert row: vcllo!VclScrolledWindow::setUserManagedScrolling+3ba2e
No crash, but I'll confirm with title change.
Comment 5 Telesto 2017-12-03 14:10:07 UTC
Opening the file is an issue already. The first page shows up, but the document is completely unresponsive 
Build ID: cc1db6f2b0ebe05ae807628778835b62df00eca2
CPU threads: 4; OS: Windows 6.3; UI render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2017-12-02_23:45:34
Locale: nl-NL (nl_NL); Calc: CL
Comment 6 QA Administrators 2018-12-04 03:48:09 UTC Comment hidden (obsolete)
Comment 7 Roman Kuznetsov 2018-12-04 06:55:21 UTC
I got a freeze of LO when I tried to open file from attach in

ID сборки: d1b41307be3f8c19fe6f1938cf056e7ff1eb1d18
Потоков ЦП: 4; ОС:Windows 6.1; Отрисовка ИП: по умолчанию; VCL: win; 
Локаль: ru-RU (ru_RU); UI-Language: ru-RU
Calc: threaded
Comment 8 Telesto 2020-06-12 15:20:46 UTC
Created attachment 161924 [details]
Very sleepy stack

File opens quite fast.. but deleting or inserting a column/row.. and it will get slow.. 


So lots of text width measuring (probably even for multiple fonts?) initiated by table rendering.. And the text shaping is not really cheap by itself.
Comment 9 QA Administrators 2022-06-13 03:26:03 UTC
Dear PeLe,

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