To many datums? World freezes

ID:164151
 
Jul 14 2007, 7:05 am
Code:
//Everything


Problem description:
Server and all it players freeze up, people can't really do anything.
I'm quite sure this ain't a infinite loop, I heard this sometimes happens when the count of datums gets to high.
I don't get any "limit" errors or anything.

Currently I'm running the game with some counting proc who will keep track of how many objects are in the world, and if there are any I'm forgetting to delete.

This error does only seem to occure after a long time of hosting.
Got any information, please share.

Thanks, Fint
Jul 14 2007, 7:09 am
I have had a problem, somewhat quite like that. For, example if a Monster were to attack me, the game would freeze up and I could'nt do a thing, then I went back to that and removed a few things and tested it, again. It worked that time, so yours could possibily the same thing. I am not, completely sure, but its better than nothing.
Jul 14 2007, 7:22 am
If you had broken the datum limit, an error message would've shown up and the game would've crashed. This definitely sounds like the result of an infinite loop somewhere in your code.
Jul 14 2007, 7:27 am
In response to Popisfizzy
Would it make sense it would freeze everybody then?
Jul 14 2007, 7:28 am
In response to Fint
Yes, infinite loops can bring the whole game to a complete halt.
Jul 14 2007, 7:30 am
In response to GhostAnime
Okay, then that's sorted out.

Ive got world.loop_checks turned to 0 right now, sincemy turn based system sometimes has such long proc calls it gives a infinite loop error causeing the player to freeze.
This only happens when battles are really long.

I'll turn it back on and see what happens.
Jul 14 2007, 7:31 am
In response to Fint
NEVER EVER set check_loops to 0, an infinite loop is definately something you do not want. There are alternative methods to give you what you want without messing up your server (too badly)
Jul 14 2007, 12:16 pm
In response to GhostAnime
GhostAnime wrote:
NEVER EVER set check_loops to 0, an infinite loop is definately something you do not want. There are alternative methods to give you what you want without messing up your server (too badly)
You might want an infinite loop if say you had a daynight system that goes on forever. However, it wouldn't recure fast enough to cause problems as long as you put the sleep() proc in there with enough seconds.
Jul 14 2007, 12:17 pm
In response to Naokohiro
Yes, you're correct... I should have said something similar to that you do not want an infinite loop that would cause that warning to come up :)
Jul 14 2007, 12:33 pm
In response to Naokohiro
It takes several million iterations to result in an infinite loop (I forget the exact amount, but I had it figured out before), by which time a game should've been shutdown and already.
Jul 14 2007, 6:07 pm
In response to GhostAnime
Sometimes an infinite loop that doesn't necessarily slow the server down causes the runtime error of "infinite loop suspected" or something like that which crashes the code that you wanted to go on forever. In this case you would have to have world.loopchecks set to zero in order for your code to work.
Jul 14 2007, 9:03 pm
In response to Naokohiro
And thats exactly what I had in my turn based system!

And the reason I made the loop thing 0, which I turned back now.
Thanks.

Going to try and figure out whats happening.