Spring RTS Engine

I've got an intel core 2 duo T6400 @ 2.0ghz, and 3 gig ram. Running Ubuntu Karmic. Trying to play Balanced Annihilation.

When I open up springlobby, that very instant one of my cores goes to 100%, and then when I open up the game, the spring engine takes up 100% of my other core. In game, I get no more than 10 fps, and when I exit the game and close springlobby, both of those processes stay running and I have to kill them manually.

I don't know whether or not the problems are related, I can live with manually killing the processes. I think I read somewhere that it had something to do with pulseaudio...? I don't have sound in game. I can figure that out later. Mostly I want to know what's up with my processors at 100%. I wouldn't think that running the game is that resource-intensive, and I KNOW it shouldn't require so much power to run just the lobby. So yea, pretty confused.

Someone have any suggestions to help me fix this?
Any help greatly appreciated Thanks!

update to 10.04 (this will fix the pulse/alsa issues that are responsible for 100% cpu in lobby)

I've been trying to study out what options I have, I see lots of people that use Karmic talking about dumping PulseAudio for Alsa. Other ones too, but mostly Alsa. What is used in 10.04? Did they quit using PulseAudio, or is it just better now?

newer version of pulseaudio, if i am right.

if you do not want to upgrade yet:
http://springrts.com/wiki/FAQ:trouble#S ... an_i_do.3F

This is not a Pulse Audio issue, this is a Spring issue and there is no way Im uninstalling something I use everyday with multiple programs to run Spring. You need to fix your code to use Alsa instead or make it work with Pulse. Out of the thousands of programs I use on Linux not one locks up two CPUs on my quadcore just opening up.

And its ridiculous that every single linux user would need to go thru this issue. This should have been fixed at release. Dont even get me started on the compile from source wiki, I dont know one OS that works on. My point is stop blaming issue with the code on other programs.

Its open source, stop bitching around and go fix it!

Nobody here needs to fix anything for you.

I am not bitching about it troll. I am bitching about someone blaming the issue on Pulse. This was a coding mistake not a Pulse audio issue. If they said yeah we know about the bug it will be fixed in the future or you can fix it then I wouldnt have an issue. I have an issue when someone blames things they have done on other people.

And you know it isn't related how exactly?
You found the bug in engine? Ok great, post the patch.

look trouble. lets assume you are 100% right.
lets assume i am an engine dev, and i read your post.
now.. how would i react:
A: "Ouh, this very client of us is right, we should do what he says."
B: "Faggot has no manners -> put on ignore list"

btw, do not bother answering, it is quite pointless

Troublesome_God, if you come in here with attitude, you will only find attitude in return. If you want some genuine help with your problems, practice some patience.

Is your Pulseaudio the latest version?

This weekend I heard from a former Fedora games packager that it's quite probably actually an OpenAL issue or an OpenAL <-> PulseAudio interaction issue, and not PulseAudio (only). Maybe someone should try sometime to compile Spring against lots of different OpenAL versions to see if that helps. It sounds like Troublesome_God is the perfect candidate for this, because this way he could determine which code really is to blame and correct the wiki

Can we refrain from "faggot" comments?

Tobi wrote:This weekend I heard from a former Fedora games packager that it's quite probably actually an OpenAL issue or an OpenAL <-> PulseAudio interaction issue, and not PulseAudio (only). Maybe someone should try sometime to compile Spring against lots of different OpenAL versions to see if that helps. It sounds like Troublesome_God is the perfect candidate for this, because this way he could determine which code really is to blame and correct the wiki

Good call

I do not have have pulse audio installed and I see this issue. I'm going direct to ALSA for all my audio; excluding whatever additional layers the game and components impose. I also see this behavior but only when the client has been idle for an extended period. I have not been able to reliably reproduce. Furthermore, I have audio disabled in the lobby client. I compiled the lobby (springlobby) my self. I assumed this was a side effect of the bittorrent client libs.

Whatever it is, pulseaudio, at least in my case, has absolutely ZERO to do with this issue. Accordingly, please stop blaming pulseaudio for every bump on the road.

your issue is different, what we are talking about is 100% of a single core usage from lobby/spring start, not blocking functionality;
and the problem "magically" disappears when upgrading PA, compiling it manually or uninstalling it, or disabling sound ( latest versions of ubuntu such as 10.4 do not have the bug anymore ), so yeah, it's 100% PA's fault for our problem, yours is simply another thing.

can you get me a stacktrace of your hang? it looks like a deadlock

gdb /path/to/springlobby
run
....wait it locks....
thread apply all bt

BrainDamage wrote: can you get me a stacktrace of your hang? it looks like a deadlock

gdb /path/to/springlobby
run
....wait it locks....
thread apply all bt

Working on it. I don't understand the gdb thing tho... I run gdb, run the game, my CPUs go to 100%, but at that point I can't enter in the part that says 'thread apply all bt' because I don't have a command prompt. Like as in if I were just in the regular old boring terminal, running some program and until I exit that program I can't enter in any more commands and whatnot. How do I do that?

Also, sometimes it works sometimes it doesn't. Twice now I've tried to get you some output, but my processors remained where they should've with my framerate where it should be instead of dropped waaaay down like when it eats up my processors.

Anyway, I'm on it. I just need help on the gdb thing. Thanks.

when it locks, send ctrl c in the console, this will give a SIGTERM which will give you back access to gdb

Licho wrote:Its open source, stop bitching around and go fix it!

Nobody here needs to fix anything for you.

Do you seriously say that every time a user comes here and haves a problem with the software? Other users response are 100 times better than your lousy "fuck you!" response.

Super Mario wrote:

Licho wrote:Its open source, stop bitching around and go fix it!

Nobody here needs to fix anything for you.

Do you seriously say that every time a user comes here and haves a problem with the software? Other users response are 100 times better than your lousy "fuck you!" response.

No, I do that every time arrogant person comes here and demands something or blames others people. People should realize it's not a help support line for paid product. Nobody here is obliged to fix other people's problems by any moral standards. Not to mention being yelled at or blamed.