[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libreoffice-documentation] DOC Meeting Minutes 2018-11-21

On 11/22/18 6:55 PM, Olivier Hallot wrote:
>      + Long editing session turns LO slow and unusable (Cathy)
>          + Some crashes. 
> AI: Send offending file to olivier for inspection  (Cathy)

I've seen the same thing happen on some of my documents.
In one case, LibO was using 15GB of Virtual RAM and 5GB of Memory RAM.
In a different case, Virtual RAM hit the 25GB point, before the system

I assumed it was because I'm using a "don't use unless you are
developer" version.
* OOo 1.1.x used to crash when there were more than 2^16 (I think) style
changes within the document;
* I've got several multi-page tables in these documents. In one
document, there was a table that was 150+ A4 pages long.

Would like copies of these documents? FWIW, the content is codes for
languages, writing systems, countries, and political subdivisions of the


To unsubscribe e-mail to: documentation+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/documentation/
Privacy Policy: https://www.documentfoundation.org/privacy

[libreoffice-documentation] DOC Meeting Minutes 2018-11-21Olivier Hallot <olivier.hallot@libreoffice.org>
Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.