openttd eats all my cpu

[Dario Panico]

Binary package hint: openttd

This game runs quite nice but eats all my CPU resources and the whole PC suffers a lot even music streaming isn't continuous.

ProblemType: Bug
Architecture: amd64
Date: Sat Oct 31 19:34:13 2009
DistroRelease: Ubuntu 9.10
Package: firefox-3.5 3.5.4+nobinonly-0ubuntu0.9.10.1
ProcEnviron:
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: firefox-3.5
Uname: Linux 2.6.31-14-generic x86_64

[Matthijs Kooijman (matthijskooijman)]

I'm kinda confused by this report, it seems like you used the bug template for firefox instead of OpenTTD? Just to confirm, does this bug actually apply to OpenTTD?

If so, could you supply your ~/.openttd/openttd.cfg file? Also, try running "openttd -d 4" from a terminal, quit openttd immediately and attach the resulting output here. Also, could you attach the output of "ps aux" while openttd is running?

Could you tell a bit more about when this bug applies? Does it apply in the main menu already, or only after starting a game? Did it occur directly after installing the game, or did it run properly before (perhaps before changing settings or upgrading)?

[Dario Panico (dariopnc-)]

yes, this bug applies to openTTD

[Dario Panico (dariopnc-)]

the bug happend after the installation of openttd, today, one day after, it eats way less CPU and I'm not sure if I can reproduce it again.

I wasn't able to provide the openttd -d 4 log because redirection doesn't work and the output is too long to be entirely copied from the terminal screen.

ps aux is useless because no other hungry process is running and openttd CPU usage has significantly lowered from ~90% to ~10%.

yesterday it was ~90% both in the menu and the game

[Matthijs Kooijman (matthijskooijman)]

Funny that it doesn't happen again. Perhaps there was some other process running that confused openttd in some way, or something else was different in your environment? If you manage to reproduce it again, let us know. If not, I'll probably close this report soon.

The debug output generated by openttd -d 4 is generated on stderr (not stdout), so use 2> log.txt to redirect.

[Giorgos Logiotatidis (seadog)]

I can confirm this bug. Openttd in Karmic eats up all my cpu

Intel Core 2 Duo @ 2Ghz
2Gb of ram
Nvidia binary drivers

[Matthijs Kooijman (matthijskooijman)]

Hi Giorgos,

Does this bug happen consistently for you? If so, could you answer my original questions:

Could you supply your ~/.openttd/openttd.cfg file? Also, try running "openttd -d 4" from a terminal, quit openttd immediately and attach the resulting output here. Also, could you attach the output of "ps aux" while openttd is running?

Could you tell a bit more about when this bug applies? Does it apply in the main menu already, or only after starting a game? Did it occur directly after installing the game, or did it run properly before (perhaps before changing settings or upgrading)?

[Michael Jensen (emjay1988)]

This bug applies to me too, I think... I have a quad core desktop (Karmic) and ps tells me that openttd takes a little over 100% (indicating one whole core - that is, it would go up to 400% if a process was taking all cores). I've attached a ps aux from various states in the game. The reason I found this issue is that when I quit the game it doesn't close. The screen just hangs with the mouse pointer over the "Yes" button (screenshot attached).

I'm using the 1.0.0 beta1 version of OpenTTD, I'm not sure if this is the right place to log this bug (I'll log it at bugs.openttd.org as well).

[Matthijs Kooijman (matthijskooijman)]

Could you see if this problem is fixed (or rather, workarounded) by installing libsdl1.2debian-pulseaudio ?

[Michael Jensen (emjay1988)]

Installing libsdl1.2debian-pulseaudio (which removed libsdl1.2debian-alsa) fixed this problem for me.

It appears that the bug is in how OpenTTD works with libsdl1.2debian-alsa.

[Michael Jensen (emjay1988)]

See http://bugs.openttd.org/task/3294 for more information