Created attachment 133414 [details] htop result - 100% CPU Version: 5.3.3.2 Build ID: 3d9a8b4b4e538a85e0782bd6c2d430bafe583448 CPU Threads: 4; OS Version: Linux 4.10; UI Render: default; VCL: gtk3; Layout Engine: new; Flatpak version Locale: cs-CZ (en_GB.UTF-8); Calc: group Empty document is enough for this behavior.. :-O
If a dialog box is open problem disappear for that moment.
Thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
I have the same result for $ flatpak run org.libreoffice.LibreOffice --writer --safe-mode
Do you need more info?
Same result for me on a clean installation of Fedora 26 (pre-release). LibreOffice 5.3.3.2 3d9a8b4b4e538a85e0782bd6c2d430bafe583448 $ flatpak info org.libreoffice.LibreOffice Ref: app/org.libreoffice.LibreOffice/x86_64/fresh ID: org.libreoffice.LibreOffice Arch: x86_64 Branch: fresh Origin: org.libreoffice.LibreOffice-origin Commit: afbd32feded570c05b71745d17df7e090b913619417423e4795600aa90552cab Location: /var/lib/flatpak/app/org.libreoffice.LibreOffice/x86_64/fresh/afbd32feded570c05b71745d17df7e090b913619417423e4795600aa90552cab Installed size: 700.9 MB Runtime: org.gnome.Platform/x86_64/3.24
Created attachment 133764 [details] strace soffice
The gist of the attached strace is this repeating set of lines poll([{fd=9, events=POLLIN}, {fd=13, events=POLLIN}, {fd=20, events=POLLIN}], 3, 230) = 1 ([{fd=9, revents=POLLIN}]) read(9, "\1\0\0\0\0\0\0\0", 16) = 8 write(9, "\1\0\0\0\0\0\0\0", 8) = 8 poll([{fd=9, events=POLLIN}, {fd=13, events=POLLIN}, {fd=20, events=POLLIN}], 3, 230) = 1 ([{fd=9, revents=POLLIN}]) read(9, "\1\0\0\0\0\0\0\0", 16) = 8 write(9, "\1\0\0\0\0\0\0\0", 8) = 8 poll([{fd=9, events=POLLIN}, {fd=13, events=POLLIN}, {fd=20, events=POLLIN}], 3, 230) = 1 ([{fd=9, revents=POLLIN}]) read(9, "\1\0\0\0\0\0\0\0", 16) = 8 write(9, "\1\0\0\0\0\0\0\0", 8) = 8 [...]
Created attachment 133765 [details] some contents of /proc/pid/ items
I also have this bug on Linux Mint 18 Xfce. And I do not even have to open an empty document, it appears only some seconds after I ran flatpak run org.libreoffice.LibreOffice (without --writer or something).
(In reply to bugzilla from comment #7) > The gist of the attached strace is this repeating set of lines > > > poll([{fd=9, events=POLLIN}, {fd=13, events=POLLIN}, {fd=20, > events=POLLIN}], 3, 230) = 1 ([{fd=9, revents=POLLIN}]) > read(9, "\1\0\0\0\0\0\0\0", 16) = 8 > write(9, "\1\0\0\0\0\0\0\0", 8) = 8 > poll([{fd=9, events=POLLIN}, {fd=13, events=POLLIN}, {fd=20, > events=POLLIN}], 3, 230) = 1 ([{fd=9, revents=POLLIN}]) > read(9, "\1\0\0\0\0\0\0\0", 16) = 8 > write(9, "\1\0\0\0\0\0\0\0", 8) = 8 > poll([{fd=9, events=POLLIN}, {fd=13, events=POLLIN}, {fd=20, > events=POLLIN}], 3, 230) = 1 ([{fd=9, revents=POLLIN}]) > read(9, "\1\0\0\0\0\0\0\0", 16) = 8 > write(9, "\1\0\0\0\0\0\0\0", 8) = 8 > > [...] What's missing from the attachment is everything leading up to those poll calls, so one would get an idea what code is doing that (i.e., what FDs 9, 13, 20 are bound to).
(In reply to Stephan Bergmann from comment #10) > What's missing from the attachment is everything leading up to those poll > calls, so one would get an idea what code is doing that (i.e., what FDs 9, > 13, 20 are bound to). bugzilla@colorremedies.com, can you provide the full strace log?
Description matches bug 108246 Comment 9 bug 108246 The issue appears to be in glib2 see https://git.gnome.org/browse/glib/commit/?id=9ba95e25b74adf8d62effeaf6567074ac932811c After rebuilding glib2 with this patch, the issue was resolved.
Weird, I have zero comment notification emails for this bug, no idea why as my preferences are set to email me. Anyway the latest flakpak update fixed this, flatpak reports Commit: 0de4a5ba7b2802a289fc10fb3ed0306f5b4ff3fe860285da465ba7e50d9eecc6 and Libreoffice reports Version: 5.3.4.2 Build ID: f82d347ccc0be322489bf7da61d7e4ad13fe2ff3
I can confirm Build ID: f82d347ccc0be322489bf7da61d7e4ad13fe2ff3 is OK. Thanks (y)