Your message dated Wed, 20 Nov 2024 02:49:20 -0800
with message-id
<caczd_tbcnctp6gyyvnhqio-qc_-bh3rmbopnlytdhk9_nzf...@mail.gmail.com>
and subject line Re: Bug#924437: [wesnoth] High CPU Load
has caused the Debian Bug report #924437,
regarding [wesnoth] High CPU Load
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
924437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924437
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wesnoth
Version: 1:1.14.5-1
Severity: normal
--- Please enter the report below this line. ---
Wesnoth produces high load on my CPU while playing. This has been already
reported also in the wesnoth forum
https://www.wesnoth.org/forum/viewtopic.php?t=48666 by other people.
The reported workaround to launch wesnoth with
OMP_WAIT_POLICY="passive" wesnoth
works for me.
--- System information. ---
Architecture:
Kernel: Linux 4.19.0-2-amd64
Debian Release: buster/sid
500 xenial updates.signal.org
500 testing ftp.de.debian.org
500 stretch download.docker.com
--- Package information. ---
Depends (Version) | Installed
=====================================-+-================
wesnoth-1.14 (>= 1:1.14.5-1) | 1:1.14.5-1
wesnoth-1.14-data (= 1:1.14.5-1) | 1:1.14.5-1
Package's Recommends field is empty.
Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---
Version: 1:1.16.1-1
On Tue, Mar 12, 2019 at 4:12 PM <[email protected]> wrote:
>
> Package: wesnoth
> Version: 1:1.14.5-1
> Severity: normal
>
> --- Please enter the report below this line. ---
>
> Wesnoth produces high load on my CPU while playing. This has been already
> reported also in the wesnoth forum
> https://www.wesnoth.org/forum/viewtopic.php?t=48666 by other people.
> The reported workaround to launch wesnoth with
>
> OMP_WAIT_POLICY="passive" wesnoth
>
> works for me.
Just cleaning up some old bugs. OpenMP support was removed by wesnoth
upstream a while back so this is no longer relevant.
Regards,
Vincent
--- End Message ---
