Bug 92064 - LO unusable with Tibetan super long paragraphs
Summary: LO unusable with Tibetan super long paragraphs
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) rc
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Not Assigned
Depends on:
Blocks: CTL-China-Minorities
  Show dependency treegraph
Reported: 2015-06-14 11:26 UTC by Elie Roux
Modified: 2023-06-18 03:14 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:

Tibetan text (with long paragraph) (187.64 KB, application/x-xz)
2015-06-14 11:26 UTC, Elie Roux

Note You need to log in before you can comment on or make changes to this bug.
Description Elie Roux 2015-06-14 11:26:30 UTC
Created attachment 116527 [details]
Tibetan text (with long paragraph)

Dear All,

In Tibetan the notion of paragraph doesn't exist, and thus texts (even hundreds of pages) are usually in only one paragraph (no line break). MS Word apparently handles that without performance issue, but LibreOffice has huge performance issues when opening or editing this kind of file. See for instance attached (xzipped) file, I didn't really manage to open it, the CPU starts to heat a lot, LO doesn't answer anymore and I have to kill it by hand. This file comes from http://www.dharmadownload.net (the second text from http://www.dharmadownload.net/pages/english/Sungbum/006_mdzod%20bdun/pages/01_mdzod%20bdun%20-%20yid%20zhin%20mdzod.html), and is a normal Tibetan text, not a long paragraph torture test made to test performance...

This bug makes LO unusable in production for Tibetan, which is a pity as many tools are in gestation for spell checking and grammar checking for Tibetan in LO, that would make it much better than Word.

This might be related to https://bugs.documentfoundation.org/show_bug.cgi?id=89666 or https://bugs.documentfoundation.org/show_bug.cgi?id=39372 but it still happens on 4.4.4~rc1 (Debian/sid), so the patches don't seem to be enough.

Thank you very much!
Comment 1 Julien Nabet 2015-06-14 12:40:44 UTC
Elie: I updated tdf#89666 because 4.5.0 won't exist. There have been some patches on 5.0 branch.
Since Michael didn't put tdf#89666 as FIXED, I suppose he thinks there's still work to do.

Anyway, I could reproduce this on pc Debian x86-64 with master sources updated today.
I noticed this on console:
warn:legacy.osl:9871:1:oox/source/helper/graphichelper.cxx:117: GraphicHelper::GraphicHelper - cannot get target frame
Comment 2 Elie Roux 2015-06-14 12:43:37 UTC
Thanks for your consideration! It would be a huge help to the Tibetan community if this could work!
Comment 3 Julien Nabet 2015-09-02 12:35:21 UTC
Version corresponds to "earliest affected" as indicated.

I'll give a try with master sources (future 5.1.0).
Comment 4 Julien Nabet 2015-09-02 18:13:22 UTC
With master sources updated today, I still get the hang when opening.
After 2 minutes, I've got this:
 warn:legacy.osl:11092:1:oox/source/helper/graphichelper.cxx:117: GraphicHelper::GraphicHelper - cannot get target frame
W: Unknown node under /registry/extlang: deprecated
W: Unknown node under /registry/grandfathered: comments
W: Unknown node under /registry/grandfathered: comments

(the 3 last lines aren't specific to this bugtracker)

Miklos: since the xz file contains an rtf, thought you might be interested in this one.
Comment 5 Elie Roux 2015-09-02 18:40:50 UTC
I have the same problem with a docx file... I can convert it into .odt and put it here if you want.
Comment 6 Julien Nabet 2015-09-02 18:57:51 UTC
(In reply to Elie Roux from comment #5)
> I have the same problem with a docx file... I can convert it into .odt and
> put it here if you want.
I suppose it may help to have different formats, so go ahead! :-)
Comment 7 QA Administrators 2016-09-20 10:28:43 UTC Comment hidden (obsolete)
Comment 8 Elie Roux 2016-09-20 16:05:03 UTC
Although there's definitely an improvement compared to 5.0 version, my LO under Debian/Sid is still very slow at opening the file indicated in the initial report, and adding or removing a character takes at least 10s, so I think it's safe to say that LO is still unusable for long Tibetan texts...
Comment 9 Xisco Faulí 2017-09-29 08:51:28 UTC Comment hidden (obsolete)
Comment 10 Elie Roux 2017-09-29 09:22:35 UTC
bug still present, Debian 9, LO
Comment 11 Buovjaga 2019-04-24 19:08:00 UTC
Takes 3 minutes to open, unusable perf after that.

Arch Linux 64-bit
Build ID: cfbb223d5666cb803539ac98918ff39b27efc6e7
CPU threads: 8; OS: Linux 5.0; UI render: default; VCL: gtk3; 
Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US
Calc: threaded
Built on 24 April 2019
Comment 12 QA Administrators 2021-06-17 03:50:19 UTC Comment hidden (obsolete)
Comment 13 Elie Roux 2021-06-17 12:06:41 UTC
still present with LO 7.1.4
Comment 14 QA Administrators 2023-06-18 03:14:38 UTC
Dear Elie Roux,

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