Forum ‹ C# ‹ Code running for too long in dev server

[azuanagames]

I keep getting the following:

>Warning: Some code has been running for longer than will be allowed in the live enviroment. The code won't be aborted since the debugger is attached, and you might be inspecting game state.

I realize I must be doing something outragous, but, I don't think that I am...

Is there a way to tell us WHERE that code may be? A hint maybe?

At least do you know of a way for me to figure out what code causes that error? If I can set a breakpoint on your "too long" detector maybe?

Azuana Games

[Oliver]

Uhm... yea, that message is not the best and could be better...

Hmm... I'm not sure but i think if you run the server in non-debug mode (Ctrl-F5), you might actually get a better message either in the developmetn server or in the error log in the admin panel.

I'll add a todo item to make it better.

Best,
Oliver

[azuanagames]

I only get the message once in a blue moon. I'm actually running in release mode. Maybe I should actually run in debug mode? If code runs for too long in production, does that go into the error log?

[Oliver]

If code runs for too long in production, does that go into the error log?

It should... The problem is that another thread has to catch the first thread (the one taking too long) and figure out where it currently is, and that doesn't always work. So, sometimes

- Oliver

[azuanagames]

Speaking of threads...

I don't handle synchronization at all. I assumed this was ok... Are there any gotchas I need to be aware of?

I'm assuming that only 1 thread is allowed access to an instance of my game at a time?

Is there ever a case where more than 1 thread can access the game class?

[Oliver]

I don't handle synchronization at all. I assumed this was ok... Are there any gotchas I need to be aware of?

That is usually totally okay. Multiple threads will call into your game, but only *if* there is a ton of congestion, and we're considering making games totally single-threaded.

- Oliver