Problems loading world - St9bad_alloc

[fabianfierro]

Hello,
I have problems loading the virtual world.
I can loguin, and select my character.  Before the game finishes loading the world, the application exits with this error message:

crystalspace.proctex.pdlight:
  Could not find light with ID
  'ffffffa8ffffffaa43ffffffc87a28fffffff450ffffffa6ffffff8c1156ffffff91ffffffbd
  ffffffe35e'
terminate called after throwing an instance of 'std::bad_alloc'
  what():  St9bad_alloc

I'm using OpenSuse 10.3 and KDE 4.
Could you please help me with this problems?

Thanks 

[Aiwendil]

Could you give please a little bit more information on you system. Maybe CPU type, Graphiccard, and how much RAM you have.

terminate called after throwing an instance of 'std::bad_alloc'
  what():  St9bad_alloc

Not completely sure, but a std::bad_alloc exception normally indicates a problem with memory. How much RAM do you have? I think you should have at least 512 MB, more won't hurt

[fabianfierro]

Thanks for your reply.

Here is the information:
AMD Sempron 2600 X86_64
Ram: 512
GForce FX5200

Y also have new information.  I created a new player and I was able to enter the game.  But After I went to another part of the world the map loading failed.  Now I can't use both players.
I hope that information helps.

Thanks

[Vornne]

Ouch...

I'm running 64 bit linux (gentoo), with an AMD 3200+, 1GB RAM, and a nvidia 6600GT. I also have 2 GB of swap, split between two hard drives. Planeshift normally runs fine, even with a server, npcclient, and two player clients.

I don't know if it's the same for you, as I have my planeshift binaries compiled in debug mode, which would make bigger binaries and use more memory... but I did a little test, "swapoff -a" first, and wait for all my swap partitions to be deactivated, then start one client and log into the test server. It was fine loading the login menu, but as I started loading (in the laanx dungeon) the memory usage went up to about 950 MB and slowed to a crawl, after I waited a while, psclient finished with the message "Killed".

So, I'm not sure if you have it already, but it would probably help to add a swap partition, or enlarge the one you have. I don't know if planeshift used more than 512 MB in my test, but when testing a while back with a debug client and a big map like bronzedoors I have seen the memory/swap usage go above 1 GB total

The memory issues are noted in the bug tracker, some of the developers are working on things that hopefully will improve it for future releases. One other thing you can do now, is turn off sound... the current sound code is buggy and uses lots of memory.