Question

Here’s the situation, I am writing the framework for a code war contest. As the code runs, for each turn, it calls a method in the library provided by each contestant. The rules of the contest is the method must return in 1 second or we kill the task calling them. We then use a default result for that turn.

The method has no support for a cancel because we cannot trust the called code to respond to a cancel. And we need to kill the thread because if we have 10 or 20 ignored background tasks then all calls going forward will provide fewer clock cycles on each call and methods that before took less than 1 second now take more.

On the plus side, the method we’re killing should have no resources open, etc. so an abort should not leave anything hanging.

Update: Two things to keep in mind here. First, this is like a game – so performance is important. Second, the worker thread is unlikely to have any resources open. If one of the called methods goes overlong, I need to abort it and move on quickly.

Answer 1

You should run each contestant in his own AppDomain with low privileges. This has several advantages:

1. It’s sandboxed
2. It can’t interact with any other code in the process
3. Force unloading an AppDomain is relatively clean.

Even if you prefer killing the thread over unloading the AppDomain I’d still put each contestant into an AppDomain to get the isolation.

Unfortunately Thread.Abort is not enough. It still executes finally clauses which can take as long as they want.