Game is only playable with --flush-stdout option? [No.]

Message

Lord Estraven · #1 Post by **Lord Estraven** » Thu Apr 12, 2012 1:28 pm

I just ran t-engine with the --flush-stdout option in an effort to track down where the huge, system-freezing memory allocations started... And to my surprise the game did not freeze, and runs ridiculously faster. Everything works. Everything is playable. But only if I use --flush-stdout, otherwise it it allocates 3 GB of RAM and triggers the OOM killer.

What's going on here?

#2 Post by **darkgod** » Thu Apr 12, 2012 1:51 pm

Really ? now that's quite interresting ... Thanks!

Lord Estraven · #3 Post by **Lord Estraven** » Thu Apr 12, 2012 2:11 pm

You're welcome.

#4 Post by **darkgod** » Thu Apr 12, 2012 2:36 pm

Can you try with --no-debug instead ?

Lord Estraven · #5 Post by **Lord Estraven** » Thu Apr 12, 2012 3:07 pm

I believe I spoke too soon...

On Ubuntu 10.04 (with a 3.2.0 kernel) --flush-stdout works fine. On Slackware 13.37 derived distros, not so much. --flush-stdout prevents the system from crashing completely, but T4 still attempts to allocate ~3GB of memory, server latency goes through the roof, and the game stops rendering anything. Strangely the Intel driver version involved is exactly the same, 2.15.0.

I will try --no-debug as you suggested...

Lord Estraven · #6 Post by **Lord Estraven** » Thu Apr 12, 2012 3:12 pm

--no-debug does not help at all on the Slackware derivatives. Will try on *buntu.

Lord Estraven · #7 Post by **Lord Estraven** » Thu Apr 12, 2012 3:34 pm

Okay, I am officially an idiot. --no-debug works fine on *buntu because, like --flush-stdout, it has no effect...

This is some kind of distro bug. Possibly in the kernel, possibly elsewhere, I really have no idea - all I know is that the huge memory allocations happen on Slackware and don't happen on *buntu, even though the Intel driver is the same version.

Maybe *buntu patches something that Slackware doesn't. Again, no idea.

*sigh* Sorry for wasting your time.

#8 Post by **yufra** » Fri Apr 13, 2012 8:27 pm

At least you can finally play the game. I felt bad that you were having such issues with it. :-/

Lord Estraven · #9 Post by **Lord Estraven** » Sat Apr 14, 2012 12:31 am

Unfortunately *buntu's grotesque lack of stability keeps me from using it as a main OS. Maybe I'll upgrade the kernel on Slack and see how that works, dunno.

Anyway I shouldn't be playing T4 too much, it might eat up too much of my time for important things (like eating, sleeping, and learning useful programming stuff). Have to commend DG for creating an interesting and addictive game though. Even if the OpenGL interface leaves something to be desired.

P.S. Is it just me or are worm masses *brutal* in this game?

#10 Post by **PureQuestion** » Sat Apr 14, 2012 1:33 am

Lord Estraven wrote:P.S. Is it just me or are worm masses *brutal* in this game?

I think Brittle Clear Oozes are the really bad multipliers. I've had entire maps just get completely clogged with the bastards.

Lord Estraven · #11 Post by **Lord Estraven** » Sat Apr 14, 2012 1:38 am

Upgraded the kernel on Slack to Liquorix 3.3.0 -> ToME4 plays fine, albeit a tad sluggish (no duh I have an Intel GPU). This is definitely some kind of kernel bug. Go figure.

ToME: the Tales of Maj'Eyal

Game is only playable with --flush-stdout option? [No.]

Game is only playable with --flush-stdout option? [No.]

Re: Game is only playable with --flush-stdout option?

Re: Game is only playable with --flush-stdout option?

Re: Game is only playable with --flush-stdout option?

Re: Game is only playable with --flush-stdout option?

Re: Game is only playable with --flush-stdout option?

Re: Game is only playable with --flush-stdout option? [No.]

Re: Game is only playable with --flush-stdout option? [No.]

Re: Game is only playable with --flush-stdout option? [No.]

Re: Game is only playable with --flush-stdout option? [No.]

Re: Game is only playable with --flush-stdout option? [No.]