Bug 119784 - LO performance problem
Summary: LO performance problem
Status: RESOLVED DUPLICATE of bug 119685
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2018-09-10 13:38 UTC by waldauf
Modified: 2018-09-10 13:51 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description waldauf 2018-09-10 13:38:25 UTC
I have LO installed on my laptop with Archlinux. I'm not sure if it is one single bug or more or any. :]

I started LO from command line. Performance issues occurred when I try to save file to XLSX with longer name with space.

Steps to Reproduce:
1. Open XLSX file from command line. This message is shown sometimes (I don't see any rule for appearing):
$ loffice /tmp/file.xlsx
(soffice:12898): GLib-GObject-WARNING **: 15:15:58.795: ../glib/gobject/gsignal.c:3492: signal name 'selection_changed' is invalid for instance '0x563d9fc98ea0' of type 'OOoAtkObjCompTxt'

2. Work with. Trying to save as XLSX with some long name, i.e. "abcd efgh ijklmn opqrs tuvwxyz.xlsx" and then LO get stuck (it's not possible to work with LO at all). In htop I see these 2 processes which every eats 100% of CPU:
/usr/lib/libreoffice/program/soffice.bin /tmp/file.xlsx --splash-pipe=5

3. I have to kill it in KDE (pressing ctrl+alt+escp). 

4. After killing LO window I see in htop "lo_kde5filepicker" processes which consumes 100% of CPU.

Actual Results:
LO gets stuck and CPU is overloaded.

Expected Results:
Normal run of LO without overloaded CPUs.

Reproducible: Always

User Profile Reset: Yes

OpenGL enabled: Yes

Additional Info:
After restarting in Save mode this bug didn't occurred but in command line I see this output:
loffice --safe-mode /tmp/file.xlsx
kf5.kio.core: Invalid URL: QUrl("abbcd efgh ijklmn opqrst uvwxyz.xlsx")

Help --> About:
Build ID: 6.1.0-2
CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; 
Locale: en-US (en_US.UTF-8); Calc: group threaded
Comment 1 Julien Nabet 2018-09-10 13:49:05 UTC
Michael/Katarina: noticing kde5, thought you might be interested in this one.
Comment 2 Katarina Behrens (Inactive) 2018-09-10 13:51:31 UTC
Lookz very much like another known issue

*** This bug has been marked as a duplicate of bug 119685 ***