Bug#1022173: Arbitrary and frequent 100% CPU load symptom with Libreoffice Writer 1:7.0.4

2022-10-21 Thread Rene Engelhard

Hi,

Am 21.10.22 um 21:23 schrieb Thorsten Glaser:

On Fri, 21 Oct 2022, Rene Engelhard wrote:


Maybe time to get hardware from this or last century even?

Excuse me! That’s so totally not acceptable.

Debian runs on such machines, and I personally also have an EeePC,
and, to reduce electronic waste, reusing of older machines is
perfectly fine.

True. But then they know or should know that stuff might become slow.

Some people might not have the budget for newer
machines or their, generally increased, power consumption.


I'd actually argue that current processors are more power-efficient than 
a Pentium M



Your statement on the other hand was dismissive and insulting on top.


And this report has a too high severity. And was on a non-supported 
distro anymore. And for backports which doesn't belong here.



Regards,


Rene



Bug#1022173: Arbitrary and frequent 100% CPU load symptom with Libreoffice Writer 1:7.0.4

2022-10-21 Thread Thorsten Glaser
On Fri, 21 Oct 2022, Rene Engelhard wrote:

> Maybe time to get hardware from this or last century even?

Excuse me! That’s so totally not acceptable.

Debian runs on such machines, and I personally also have an EeePC,
and, to reduce electronic waste, reusing of older machines is
perfectly fine. Some people might not have the budget for newer
machines or their, generally increased, power consumption.

Your statement on the other hand was dismissive and insulting on top.

bye,
//mirabilos



Bug#1022173: Arbitrary and frequent 100% CPU load symptom with Libreoffice Writer 1:7.0.4

2022-10-21 Thread Robin
Am Fri, 21 Oct 2022 15:21:11 +0200
schrieb Rene Engelhard :

Hello Rene,

sorry for having sent this report to the wrong listing. I followed the 
instructions found here:
https://www.debian.org/Bugs/Reporting
there was nothing mentioned about different treatment for backports at all, and 
I'm not that experienced in bug reporting.

>Let's merge them since the description sounds familiar enough.
Please feel free to assign, move or merge with whatever you consider to be 
appropriate.

>Wow.
I have no other system running besides this old but fast 32bit notebook, which 
is still absolutely fit and fine for everyday work (I'm not compiling or 
programming, being translator, not programmer). It is even fit for gimp image 
manipulation of large images, or dual head multimedia display up to 3000kbps 
and surfing the web fast and fluently, you'd not guess its age.

> Buster is out of life. 
I know, but I'm running LTS until June 2024 on this notebook, since some of its 
hardware components are not supported properly in bullseye anymore by the 
drivers. Somebody decided to remove the needed code.
 
> Does it still happen with bullseye? (Assume so since the buster-backports 
> version is built from bullseye)
> Does it happen with the version in bullseye-backports?
I'll check this both as soon as possible. Will have to setup a parallel 
bullseye install here first for testing. Then I can definitely state whether it 
happens with the non backported bullseye version of Libreoffice also. Maybe I 
can even run a test on bookworm, but I'm not sure by now whether and when I can 
free up some time for all this testing in OS versions I have not running or 
even installed here.

> (Btw, you want to upgrade to deb11u4 backport whenever it is approved 
> immediately to fix a security bug)
Many thanks for this security warning, I'll watch out, as always, for the 
update.

Regards
Robin



Bug#1022173: Arbitrary and frequent 100% CPU load symptom with Libreoffice Writer 1:7.0.4

2022-10-21 Thread Rene Engelhard



severity 1022173 minor
forcemerge 964549 1022173
thanks

Hi,

Am 21. Oktober 2022 14:39:13 MESZ schrieb Robin :
>Looks possibly like a regression of a bug reported in 2020 already for an 
>older Libreoffice release:
>#964549

Well, that one never was handled at all, actually. It's open still.

Let's merge them since the description sounds familiar enough.

Regards

Rene
-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.



Bug#1022173: Arbitrary and frequent 100% CPU load symptom with Libreoffice Writer 1:7.0.4

2022-10-21 Thread Rene Engelhard



notfound 1022173 1:7.0.4-4+deb11u3_bpo10+1
found 1022173 1:7.0.4-4+deb11u3
tag 1022173 + moreinfo
thanks

Am 21. Oktober 2022 14:39:13 MESZ schrieb Robin :
>Package: libreoffice-writer
>Version: 1:7.0.4-4+deb11u3_bpo10+1

No. You even say the correct version below:

1:7.0.4-4+deb11u3~bpo10+1

The _ is just because the UI displays the ~ wrongly.

In a related note, read the docs. https://backports.debian.org/Instructions/ 
clearly says:

"Report Bugs

Please report bugs in backported packages to the backports mailing list and NOT 
to the Debian BTS!
"


>CPU threads: 1; 
(...)
> $ lscpu
> Architecture: i686
> CPU op-mode(s): 32-bit
> Byte Order: Little Endian
> Address sizes: 32 bits physical, 32 bits virtual
> CPU(s): 1
> On-line CPU(s) list: 0
> Thread(s) per core: 1
> Core(s) per socket: 1
> Socket(s): 1
> NUMA node(s): 1
> Vendor ID: GenuineIntel
> CPU family: 6
> Model: 13
> Model name: Intel(R) Pentium(R) M processor 1.73GHz

Wow.
Maybe time to get hardware from this or last century even?

>$ lsb_release -a
>No LSB modules are available.
>Distributor ID:Debian
>Description:   Debian GNU/Linux 10 (buster)
>Release:   10
>Codename:  buster

Buster is out of life. 

Does it still happen with bullseye? (Assume so since the buster-backports 
version is built from bullseye)
Does it happen with the version in bullseye-backports?

(Btw, you want to upgrade to deb11u4 backport whenever it is approved 
immediately to fix a security bug)
Regards

Rene
-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.



Bug#1022173: Arbitrary and frequent 100% CPU load symptom with Libreoffice Writer 1:7.0.4

2022-10-21 Thread Robin
Package: libreoffice-writer
Version: 1:7.0.4-4+deb11u3_bpo10+1
Severity: important

When editing a Document in Libreoffice everything is fine, even when it's a 
very large document > 150 pages and this lasts some hours. But the behaviour 
described below is independent of document size.

When minimising the Libreoffice window, or putting it into background, while 
working in other program windows, after an arbitrary period CPU load raises to 
100%, causing cooling fan to run at constant highest speed and slowing down 
your work remarkably. Sometimes this starts after some minutes already, 
sometimes after some hours only after the Libreoffice window was lost focus. It 
is unpredictable. Workaround for this I found is to maximise or restore or make 
active Libreoffice window, which will stop the 100% load immediately, going 
down to the default 1% to 5 % system load. It will happen again and again, 
independent of which document is edited. This behaviour is quite anoying when 
working in multiple documents/drawings at the same time or when an internet 
research is needed to complete a text document, or an image is to be prepared 
for the document in between, since you can't predict when Libreoffice starts 
going mad. It happens even when working in two Libreoffice Writer documents 
parallel in two windows. If the first window has not the focus, libreoffice 
will stall after some time.

Once it has started this, you can repeatedly switch the windows, causing 
allways the CPU go up to 100% and switching from 800MHz to 1,7GHz mode, if the 
first Libreoffice Writer window looses focus, either by minimising it or by 
activating any another window, so the Libreoffice window concerned is in 
background, and CPU is going back to normal immediately always when first 
Libreoffice Writer window gets active again. 

Example:
activate the 1st Libreoffice window → 2% System load (0% soffice.bin)
activate any other window including 2nd Libreoffice document windows: → 100% 
System load (98% soffice.bin)
activate the 1st Libreoffice window → 2% System load (0% soffice.bin)
activate any other window including 2nd Libreoffice document windows: → 100% 
System load (98% soffice.bin)
activate the 1st Libreoffice window → 2% System load (0% soffice.bin)
minimise to tray the 1st Libreoffice window → 100% System load (98% soffice.bin)
activate the 1st Libreoffice window → 2% System load (0% soffice.bin)
and so on...

No other program I know of shows this or a similar behaviour for me.

Now I found out it can get set back temporarly to accept not having the focus 
by re-saving the document, even when nothing has been changed since the last 
saving. Then the CPU load will stay for some time at normal again, but again 
after an arbitrary period the issue will start anew, exactly as described 
above. You can repeat this also unlimited times, so no proper work is possible.

—This also happens when running Libreoffice in protected mode exactly the same.
—The behaviour is independend of size of the document.
—It happens with all documents.
–This is not restricted to Writer, same happens to Calc. Other Libreoffice 
components may be affected also.
—Nice down soffice.bin doesn't change things, but prevents at least other 
programs from being slowed down by this exorbitant CPU usage of Libreoffice, so 
system stays responsible.
—When Libreoffice is ideling in its document selection launch (where you can 
select previously used documents from a screen) without a document being opened 
in one of its components, this issue doesn't happen at all.

Looks possibly like a regression of a bug reported in 2020 already for an older 
Libreoffice release:
#964549

And also this even older report (from 2018) might be of some interest:
https://bugs.documentfoundation.org/show_bug.cgi?id=117684

Please, could you finally fix this issue? It's annoying and keeps from using 
Libreoffice, since it drains notebook accu.

Technical data:

Libreoffice (as reported by "about" in GUI) :
Installed version:
Version: 7.0.4.2
Build ID: 00(Build:2)
CPU threads: 1; OS: Linux 4.19; UI render: default; VCL: gtk3
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Debian package version: 1:7.0.4-4+deb11u3_bpo10+1
Calc: threaded

$ apt-cache policy libreoffice* | grep -v '(keine)' | grep -B1 Installiert
libreoffice-math:
  Installiert:   1:7.0.4-4+deb11u3~bpo10+1
libreoffice-gtk3:
  Installiert:   1:7.0.4-4+deb11u3~bpo10+1
libreoffice-core:
  Installiert:   1:7.0.4-4+deb11u3~bpo10+1
libreoffice-l10n-de:
  Installiert:   1:7.0.4-4+deb11u3~bpo10+1
libreoffice-base-core:
  Installiert:   1:7.0.4-4+deb11u3~bpo10+1
libreoffice-impress:
  Installiert:   1:7.0.4-4+deb11u3~bpo10+1
libreoffice-help-de:
  Installiert:   1:7.0.4-4+deb11u3~bpo10+1
libreoffice-help-common:
  Installiert:   1:7.0.4-4+deb11u3~bpo10+1
libreoffice-style-colibre:
  Installiert:   1:7.0.4-4+deb11u3~bpo10+1
libreoffice-writer:
  Installiert: