If Linux UQM crashes on you all the time...

	Welcome, Guest. Please login or register. Did you miss your activation email? January 19, 2025, 04:39:58 am

News: Celebrating 30 years of Star Control 2 - The Ur-Quan Masters

The Ur-Quan Masters Discussion Forum

The Ur-Quan Masters Re-Release

Technical Issues (Moderator: Death 999)

If Linux UQM crashes on you all the time...

« previous next »

Pages: [1]

Author

Topic: If Linux UQM crashes on you all the time... (Read 2575 times)

Michael Martin
Core Team
*Smell* controller

Offline

Posts: 387

If Linux UQM crashes on you all the time...
« on: December 27, 2003, 04:50:19 am »

There have been a number of bug reports involving the Linux version of 0.3 crashing every few minutes, particularly in conversation screens.

This has been linked with use of the new threading library in Linux 2.6 (which Red Hat also uses in some of the 2.4 kernels.) See [link=http://uqm.stack.nl/cgi-bin/bugs/show_bug.cgi?id=561]the Bugzilla report[/link] for full details. I reproduce Jeff Cook's workaround:

Quote

...if I force usage of the old linuxthread libs with "LD_ASSUME_KERNEL=2.4.19 uqm" I can play for hours with out a lockup.

I don't actually have an NPTL system, but Mika has done further expermentation and has deduced that we're leaking thread IDs. This workaround is not perfect, but it will let it go for about six times as long before the thread pool is exhausted. (So, two hours instead of 20 minutes...)

Other than that, save frequently, and if you find yourself doing a lot of seeking back and forth in a conversation, save and quit immediately afterwards and you'll be able to reset the "timer", such as it is. (Each seek spawns several threads to handle the shift, and UQM will crash after spawning a certain number of them. This number seems to be much larger by default for LinuxThreads than for NPTL.)


	Logged

Zeep-Eeep
Enlightened

Offline

Gender: Male

Posts: 917

Good Grief

To to make sure I get this...
« Reply #1 on: December 28, 2003, 12:14:39 pm »

Is that command "ASSUME_THREAD uqm" thing supposed to be used when running the configure script, when running "make" on the command line when running UQM?

Thanks for the bug fix.


	Logged

What sound does a penguin make?

meep-eep
Forum Admin
Enlightened

Offline

Posts: 2847

Re: If Linux UQM crashes on you all the time...
« Reply #2 on: December 28, 2003, 06:32:33 pm »

When running. Or rather, *to* run.
'<VAR>=<value> <command>' means run <command> with the environment variable <var> set to <value> (in Bash).
Alternatively, you can just do "export LD_ASSUME_KERNEL=2.4.19" and then start uqm normally, but "LD_ASSUME_KERNEL" will remain set then for yous shell after uqm finished, so you'd have to do "unset LD_ASSUME_KERNEL" lest you influence programs you run after that in the same shell.
(Using (t)csh you'd use "setenv LD_ASSUME_KERNEL 2.4.19" instead of export)

Btw, it's not a bug fix, it's a work-around. And probably not even that, as the problem will only take a while longer to show itself, but will still exist.


« Last Edit: December 28, 2003, 06:33:42 pm by meep-eep »	Logged

“When Juffo-Wup is complete
when at last there is no Void, no Non
when the Creators return
then we can finally rest.”

Zeep-Eeep
Enlightened

Offline

Gender: Male

Posts: 917

Good Grief

fixed
« Reply #3 on: December 28, 2003, 09:24:22 pm »

Thanks for addressing this problem. The work around seems to work...which is great. It saves me from kicking myself when I don't save every few mnutes.


	Logged

What sound does a penguin make?

Michael Martin
Core Team
*Smell* controller

Offline

Posts: 387

Re: If Linux UQM crashes on you all the time...
« Reply #4 on: December 28, 2003, 10:02:34 pm »

Actually, it was the bug reporter Jeff Cook who gave us the workaround, not us

But we do think we know what we need to about it now to get an actual fix.


	Logged

Michael Martin
Core Team
*Smell* controller

Offline

Posts: 387

Re: If Linux UQM crashes on you all the time...
« Reply #5 on: January 10, 2004, 03:33:21 am »

We've now committed what we believe to be an "actual fix" to this problem to CVS.


	Logged

Pages: [1]

« previous next »