Steps: 1. Open Writer 2. Tools > Options > LibreOffice > Paths 3. One cpu core spikes to 100% 4. Select LibreOffice > Font and cpu core returns to normal 5. Select LibreOffice > Paths and cpu is still fine 6. Select AutoCorrect entry and double-click or click 'Edit' button 7. One cpu core spikes to 100% Version: 6.0.0.0.alpha0+ Build ID: 888f3f18cf42ca08f55a5e4826b4298f391e14aa CPU threads: 2; OS: Linux 4.4; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); Calc: group This doesnt happen when running the same version in gtk2.
Can't reproduce with the following build. Checked using htop, no cores had more than 10% utilization. Version: 6.0.0.0.alpha0+ Build ID: 4815b6f7c70cca5a226163caaaab8a227f32be48 CPU threads: 16; OS: Linux 4.10; UI render: default; VCL: gtk3; Locale: en-GB (en_US.UTF-8); Calc: group
I don't see it either
The version i tested in the description is moggi's daily updater build on my Linux Mint 18 desktop. I just tested a git build on my laptop which i did some time ago on Ubuntu Mate 16.04 and it shows the same issue. Possibly this issue only shows with the gtk 3.18.9 which is available in Ubuntu 16.04 LTS. Version: 6.0.0.0.alpha0+ Build ID: 6580e171ad054dca38f55822e67a400191cecdf5 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); Calc: group
Is this perhaps a duplicate of bug #108246 ? i.e. what's the version of glib2 ? https://git.gnome.org/browse/glib/commit/?id=9ba95e25b74adf8d62effeaf6567074ac932811c
(In reply to Caolán McNamara from comment #4) > Is this perhaps a duplicate of bug #108246 ? i.e. what's the version of > glib2 ? Not sure if its a duplicate. glib2.0-0 is version 2.48.2.
Still happens on today's build - 2017-09-18_00.33.41 Version: 6.0.0.0.alpha0+ Build ID: dd5868409ae430f9c9ffea18ea7e287a65cfa2ab CPU threads: 2; OS: Linux 4.4; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); Calc: group
Reproducible for me with Version: 6.0.0.0.alpha0+ Build ID: 69e62bbebc1f4809101df0c694a930b07dbc194d Threads CPU : 4; OS : Linux 4.4; UI Render : par défaut; VCL: gtk3; Ubuntu_16.04_x86-64 Locale : fr-FR (fr_FR.UTF-8); Calc: single built today at home under Ubuntu 16.04 x86-64 Set to NEW. Best regards. JBF
run it under gdb and ctrl+c when its busy and get a bt, cont to continue, ctrl+c again, and repeat a few times sampling what the bt is and see if its typically the same bt and if so then paste that here ?
I can't reproduce it in Version: 6.0.0.0.alpha0+ Build ID: dd5868409ae430f9c9ffea18ea7e287a65cfa2ab CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group Ubuntu 17.04
Created attachment 136346 [details] backtrace (In reply to Caolán McNamara from comment #8) > run it under gdb and ctrl+c when its busy and get a bt, cont to continue, > ctrl+c again, and repeat a few times sampling what the bt is and see if its > typically the same bt and if so then paste that here ? pressed ctrl+c in the terminal window when it was busy, but that closed LO and exited gdb, so not sure how to repeat 'cont to continue, ctrl+c again'. so then repeated the steps in comment 0 in gdb and attached in the log.
(In reply to Caolán McNamara from comment #8) > run it under gdb and ctrl+c when its busy and get a bt, cont to continue, > ctrl+c again, and repeat a few times sampling what the bt is and see if its > typically the same bt and if so then paste that here ? Will try to get a backtrace but before I need to rebuild in debug mode. Some observations: it seems that cpu is busy in options dialogs with "add" button. For example in the dialog Macro Security, the first tab Security Level does not consume more than 10% of one cpu while the second tab Trusted Source consumes almost one cpu (> 70%). Other affected options dialogs: each "Edit Path" dialog, Certificate Path, Expert configuration dialog is affected too but it as an Edit button, not an Add button. But not: - "Time Stamping Authority URLs" dialog - Advanced dialog Best regards. JBF
@JBF, you can also use a debug daily build...
Created attachment 136358 [details] my backtrace Here is the log of my gdb session with several backtrace. Hope this helps. I can do more tests if needed. Version: 6.0.0.0.alpha0+ Build ID: 9d837f19d1bf4cfbdee528e027f5b72d9b1da73d CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; Ubuntu_16.04_x86-64 Locale: fr-FR (fr_FR.UTF-8); Calc: single Best regards. JBF
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Not reproducible for me with versions 6.1.x and current master, both built at home under Ubuntu 18.04 x86-64. Closing as WorksForMe. Please, feel free to reopen if you disagree. Best regards. JBF