aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/ThirdParty/SmartThreadPool/SmartThreadPool.cs (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Massive tab and trailing space cleanupMelanie Thielker2017-01-051-817/+817
|
* workaround potencial memory leakUbitUmarov2016-08-221-0/+3
|
* workaround potencial memory leakUbitUmarov2016-08-221-0/+1
|
* Fix crash due to setting Thread.name after thread start.Roger Kirkman2016-05-121-2/+3
| | | | Signed-off-by: Diva Canto <diva@metaverseink.com>
* Undo "Revert "Small changes to threading to send thread names to unmanaged ↵BlueWall2014-09-171-1/+1
| | | | | | | | threads. Needs Mono 3.6+ to see thread names in utilities like top -H . Some formatting of the thread name to fin in the 16 byte limit on Linux. Please test on Windows to see if the work has any adverse effects."" Fix for break in next commit This reverts commit 376fab140227e92dbd841436509a97b87c9e7792.
* Revert "Small changes to threading to send thread names to unmanaged ↵BlueWall2014-09-171-1/+1
| | | | | | | threads. Needs Mono 3.6+ to see thread names in utilities like top -H . Some formatting of the thread name to fin in the 16 byte limit on Linux. Please test on Windows to see if the work has any adverse effects." This reverts commit af286d5fcb688e8b64202b6deca4f249e9a2b6b8. Issue with Jenkins builds
* Small changes to threading to send thread names to unmanaged threads. Needs ↵BlueWall2014-09-171-1/+1
| | | | Mono 3.6+ to see thread names in utilities like top -H . Some formatting of the thread name to fin in the 16 byte limit on Linux. Please test on Windows to see if the work has any adverse effects.
* Fix SmartThreadPool line endings in recent update from dos to unixJustin Clark-Casey (justincc)2013-05-011-1732/+1732
|
* Update SmartThreadPool to latest version 2.2.3 with a major and minor change.Justin Clark-Casey (justincc)2013-05-011-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
* Assign the SmartThreadPool name in the constructorOren Hurvitz2013-01-191-1/+7
| | | | This is required because some threads are created in the constructor, so assigning the name afterwards would be too late.
* * Allow SmartThreadPool to be initialized without setting max stack size ↵John Hurliman2009-10-221-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."
* * This is Melanie's XEngine script engine. I've not tested this real well, ↵Teravus Ovares2008-05-301-0/+1438
however, it's confirmed to compile and OpenSimulator to run successfully without this script engine active.
generated by cgit v1.1 at 2024-11-20 12:22:24 +0000