Search found 9 matches
- Mon Feb 20, 2006 3:06 am
- Forum: Testing and Bug reports
- Topic: Mutating Commander Name
- Replies: 8
- Views: 7740
Any hints?
What are the likely areas to stare at? I'm guessing that player_name and the cdrName variables are a good place to start at. Anything else I should take a look at? I can reproduce the problem easily enough by docking, saving the commander, going to the long distance screen and searching for a planet...
- Fri Feb 17, 2006 9:46 pm
- Forum: Testing and Bug reports
- Topic: Mutating Commander Name
- Replies: 8
- Views: 7740
- Thu Feb 16, 2006 1:56 pm
- Forum: Oolite-Linux
- Topic: Oolite consumes all memory
- Replies: 58
- Views: 42452
Repeatability
I often trade between Ensoreus and Ararus (Galaxy 1) as they are the classic Rich-Industrial/Poor Agricultural close pair for good trading runs. Ararus is an anarchy world and it is there that I have had almost all of the memory consumers wipeouts. I rarely make more than two or three runs to the Ar...
- Thu Feb 16, 2006 3:13 am
- Forum: Oolite-Linux
- Topic: Source users: source tree layout will be changing
- Replies: 6
- Views: 9360
Current SVN doesn't compile...
Something seems to have been messed up between 1.62 and the current SVN (which reports 252). I don't seem to have Cocoa/Cocoa.h on my system - should I have? Is that something OS X specific? OOCocoa/OOCocoa.h I can see. toby@nexus:~/progs/svn/oolite/trunk$ make Making all for app oolite... Compiling...
- Thu Feb 16, 2006 3:02 am
- Forum: Oolite-Linux
- Topic: Oolite consumes all memory
- Replies: 58
- Views: 42452
Better gdb traces...
Here's a few proper stacks (this time from my AMD64 Ubuntu box which is working again :-) ). It looks like we are deep in the AI - I have no idea whether all these stacks are helping. Let me know if you want me to run with some debug code - normally I run at about 40% cpu usage in oolite so I have p...
- Fri Feb 10, 2006 2:58 am
- Forum: Oolite-Linux
- Topic: Oolite consumes all memory
- Replies: 58
- Views: 42452
tjwhaynes: I suspect that for the trace with the bellf()s, the stack was corrupted. bellf() is defined in legacy_random.c; it only calls printf() and randrot_rand() (which is a leaf function). Further investigation shows tha my_glDisable(), which is also on your first stack trace, is never called a...
- Wed Feb 08, 2006 1:38 am
- Forum: Oolite-Linux
- Topic: Oolite consumes all memory
- Replies: 58
- Views: 42452
Statistical debugging of the memory hog
I realised that oolite was stuttering again and shoved it into window mode and fired up gdb. This is the result of doing a few rounds of Ctrl-C, bt, cont - there seems to be significant stack recursion through bellf - is this intentional? I don't know if this is useful - I might pull down the latest...
- Sun Feb 05, 2006 7:43 pm
- Forum: Oolite-Linux
- Topic: Oolite consumes all memory
- Replies: 58
- Views: 42452
I've also seen this (Fedora Core 4 x86 laptop)
After trading and playing with a new commander on my x86 laptop (my AMD64 monster-box is ill :cry: ) on the 1.62-2 autopackage install, I also hit this. I'd probably made fifteen planetary trips at the point where it starting swapping and became unresponsive. I took a look at top and it had hit 1.6G...
- Wed Sep 28, 2005 12:37 am
- Forum: Oolite-Linux
- Topic: Death By Docking Computer
- Replies: 7
- Views: 11062
Death By Docking Computer
You just can't trust these dodgy deals in the back of the space port. I go up to this fella, he says "wanna docking computer? Your approach were mighty shakey. Going cheap". So I pays my money and kicks off to the next system. Get my approach all lined up and then remember the new toy - pr...