ContextSwitchDeadlock was detected

When I run the following code in C# to access to database schema with a table named CheckListBilling_Transact_Tbl that has 925601 rows.

public void displayProducts()


  DateTime t1 = new DateTime();

  DateTime t2 = new DateTime();




    //Instantiate OracleDataAdapter to create DataSet

    productsAdapter = new OracleDataAdapter();


    //Fetch Product Details

    productsAdapter.SelectCommand = new OracleCommand("SELECT * FROM

                    CheckListBilling_Transact_Tbl", conn);



   //Instantiate DataSet object

   productsDataSet = new DataSet("productsDataSet");


   //take time before execute the data adapter

   t1 = DateTime.Now;


   //Fill the DataSet with data from ‘Products’ database table

   productsAdapter.Fill(productsDataSet, "Products");


   t2 = DateTime.Now;


   //TimeSpan td1 = new TimeSpan(t1.Hour, t1.Minute, t1.Second);

   //TimeSpan td2 = new TimeSpan(t2.Hour, t2.Minute, t2.Second);


   TimeSpan td = t2.Subtract(t1);

   //setting ‘productsDataSet’ as  the datasouce and ‘Products’ table

   //as the table to which the ‘productsDataGrid’ is Bound.

   productsDataGrid.DataSource = productsDataSet;

   productsDataGrid.DataMember = "Products";


 catch (Exception ex)


   //Display error message





I got the following error:

ContextSwitchDeadlock was detected

Message: The CLR has been unable to transition from COM context 0x2090a8 to COM context 0x209218 for 60 seconds. The thread that owns the destination context/apartment is most likely either doing a non pumping wait or processing a very long running operation without pumping Windows messages. This situation generally has a negative performance impact and may even lead to the application becoming non responsive or memory usage accumulating continually over time. To avoid this problem, all single threaded apartment (STA) threads should use pumping wait primitives (such as CoWaitForMultipleHandles) and routinely pump messages during long running operations.


I found a link “” for this error. Basically going to Visual Studio 2008 menu:

Debug -> Exceptions -> Managed Debug Assistants

and unchecking the ContextSwitchDeadlock item

It works.

It tooks 4 minutes and 25 seconds to populate the DataGridView but so far so good.

Software used:

Visual Studio 2008 C#

Oracle 11g Database

About chanmingman

Since March 2011 Microsoft Live Spaces migrated to Wordpress ( till now, I have is over 1 million viewers. This blog is about more than 50% telling you how to resolve error messages, especial for Microsoft products. The blog also has a lot of guidance teaching you how to get stated certain Microsoft technologies. The blog also uses as a help to keep my memory. The blog is never meant to give people consulting services or silver bullet solutions. It is a contribution to the community. Thanks for your support over the years. Ming Man is Microsoft MVP since year 2006. He is a software development manager for a multinational company. With 25 years of experience in the IT field, he has developed system using Clipper, COBOL, VB5, VB6, VB.NET, Java and C #. He has been using Visual Studio (.NET) since the Beta back in year 2000. He and the team have developed many projects using .NET platform such as SCM, and HR based applications. He is familiar with the N-Tier design of business application and is also an expert with database experience in MS SQL, Oracle and AS 400.
This entry was posted in .Net. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.