The difference between native thread termination and managed thread abort

When the managed thread is aborted, an exception is introduced at the thread's current instruction pointer. This allows the finally blocks to execute as the thread winds down.

The runtime is also aware of code that are performing non-interruptable operations like manipulating system state and so it will delay introducing the abort exception until a safe point has reached.

Terminating a native thread does not free the user-mode stack. The thread can hold onto locks that after termination will remain in the acquired state. This thread could also have been modifying critical system state which gets corrupted when interrupted. If you terminate a native thread, you should probably be terminating the process as well.

Comments

Post a Comment

Popular posts from this blog

Tutorial: Using Google Cloud Storage from C# and .NET

There is almost no samples or documentation available anywhere for this, so I thought I would write this up myself as using the storage from GCS (similar to Amazon S3 and Azure Blob Storage) is one of the most basic things which people do with the cloud. The very first thing to do after creating the C# project in Visual Studio is to install the Nuget package mentioned here: https://www.nuget.org/packages/Google.Apis.Storage.v1/ There is a lot of confusion with multiple packages available, but this is what you want for GCS. Install-Package Google.Apis.Storage.v1 You are going to need to reference the following namespaces: using Google.Apis.Auth.OAuth2; using Google.Apis.Storage.v1; Setup the basic items you need for making the calls: private static ClientSecrets _clientSecrets = new ClientSecrets();         private static UserCredential _userCredential = null;         private static StorageService _storageService = new StorageService();         private const string
Read more

Late 2008 Macbook only giving 1.5 gb/s speed with 6 gb/s Intel SSD?

You may find it online that this is due to the nvidia chipset used in the macbook. There is apparently a bug which causes all Intel SSDs to run at 1.5 gb/s with this chipset. What is interesting is that I have an old HP ML115 server in the basement which was also showing the speed of the Intel SSD as 1.5 gb/s whereas another SSD from PNY was able to do 3 gb/s which is what the motherboard actually supports. Guess what? That server motherboard also uses an nvidia chipset. I spent the whole day tinkering with the server trying to figure out why my expensive Intel SSD is giving me 1.5 gb/s while the cheap PNY was giving me 3 gb/s. No matter what I did, it did not work - including connecting the Intel SSD to a RAID controller card and using it without RAID. Some people have given the workaround to connect the hard drive to the CD drive connector which uses the Intel chip and not nvidia one. What I did is to put the PNY SSD from my server in the macbook. It consistently gave 3 gb/s
Read more

Enable Visual Studio to use more than 2GB of memory

Very useful when you have more memory: http://mkwec.de/2010/01/08/make-visual-studio-use-more-than-2-gig-of-memory/ "Using Visual Studio can be quite frustrating: even having a big quad processor 8 gig SSD raid machine it will still complain not being able to complete an operation because there is not enough “storage” available. Ever seen this “Not enough storage is available to complete this operation.”-Message in large solutions with many projects? Actually this “storage” means memory and you can use the following steps to provide more memory to visual studio: Windows XP users only:  add the /3GB switch to your boot.ini (make sure you backup your old boot.ini before) Windows Vista users only: from the Visual Studio command prompt run: BCEDIT /Set IncreaseUserVa 3072 Apply large address awareness to visual studio by running: editbin /LARGEADDRESSAWARE devenv.exe in your <path-to-VS>/Common7/IDE (make sure you backup your old devenv.exe) Reboot Now Visual Stu
Read more