aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/ThirdParty/SmartThreadPool/SmartThreadPool.cs (unfollow)
Commit message (Collapse)AuthorFilesLines
2013-05-01Fix SmartThreadPool line endings in recent update from dos to unixJustin Clark-Casey (justincc)1-1732/+1732
2013-05-01Update SmartThreadPool to latest version 2.2.3 with a major and minor change.Justin Clark-Casey (justincc)1-1448/+1732
SmartThreadPool code comes from http://www.codeproject.com/Articles/7933/Smart-Thread-Pool This version implements thread abort (via WorkItem.Cancel(true)), threadpool naming, max thread stack, etc. so we no longer need to manually patch those. However, two changes have been made to stock 2.2.3. Major change: WorkItem.Cancel(bool abortExecution) in our version does not succeed if the work item was in progress and thread abort was not specified. This is to match previous behaviour where we handle co-operative termination via another mechanism rather than checking WorkItem.IsCanceled. Minor change: Did not add STP's StopWatch implementation as this is only used WinCE and Silverlight and causes a build clash with System.Diagnostics.StopWatch The reason for updating is to see if this improves http://opensimulator.org/mantis/view.php?id=6557 and http://opensimulator.org/mantis/view.php?id=6586
2013-01-19Assign the SmartThreadPool name in the constructorOren Hurvitz1-1/+7
This is required because some threads are created in the constructor, so assigning the name afterwards would be too late.
2010-05-18While examining our 10,10,10 issue I discovered that several threads were ↵Tom Grimshaw1-8/+5
locked with each other in an unusual place; I've moved the piece of code inside a lock[] context and so far it's looking promising.
2009-10-22* Allow SmartThreadPool to be initialized without setting max stack size ↵John Hurliman1-1/+5
(like the original implementation) * Only initialize Util's SmartThreadPool if it is actually being used * No longer initializing Util's SmartThreadPool with a custom max stack size. From MSDN: "Avoid using this constructor overload. The default stack size used by the Thread(ThreadStart) constructor overload is the recommended stack size for threads."
2008-05-30* This is Melanie's XEngine script engine. I've not tested this real well, ↵Teravus Ovares1-0/+1438
however, it's confirmed to compile and OpenSimulator to run successfully without this script engine active.