ID:188902
 
If anyone has a list of the more prominent crash bugs in BYOND right now, could you please post it for me? I'd like to review it and make the necessary changes to my games.

By crash bugs, I am referring to anything that would 1) shut the program down with no warning, 2) perform an illegal operation


~Pola~

Runtimes are evil!!!! Curse them with all your coding power!! Dont let more than 2 slip by, otherwise they'll crash any server that's been up for awhile, such as those '24/7' servers that stay up about ...14/6...

[EDIT]
My computer is a relativly slower CPU, an AMD 501Mhz. Sometimes when hosting certain games with alot of procs running at once, I've had instances where DS would freeze. It's not really a big problem, but if your game is to be user friendly, and since not everyone has a fast CPU, be careful on the number of proc's running at any one time.
In response to FenrirXIII
Hes not talking about runtime errors, hes talking about errors with the byond program, errors that shouldn't be there. Like, for example, you program something perfectly, yet it still crashes, that would be a crash bug.
Polatrite wrote:
If anyone has a list of the more prominent crash bugs in BYOND right now, could you please post it for me? I'd like to review it and make the necessary changes to my games.

By crash bugs, I am referring to anything that would 1) shut the program down with no warning, 2) perform an illegal operation

I don't think there are any known except one: If you use a form in an HTML document, the data it sends back can potentially too big for BYOND to handle. (I suspect one reason is the standard way of encoding certain chars as %xy, which makes them use up space faster.) BYOND only handles the limited GET method for forms, not POST.

Anything else seems to be unpredictable.

Lummox JR