• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2073
  • Last Modified:

The CLR has been unable to transition from COM context 0x1a0990 to COM context 0x1a0b00 for 60 seconds. (?????)

Can anyone give me a clue here?  It pops up while I'm debugging my C# 2.0 VS 2005 application, as I'm looking at the different variables, trying to figure out what paths my app is taking....

The CLR has been unable to transition from COM context 0x1a0990 to COM context 0x1a0b00 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.
0
gurteen
Asked:
gurteen
  • 3
1 Solution
 
Mikal613Commented:
what line does this happen?
0
 
devsolnsCommented:
Do you have the [STAThread] attribute anywhere?  If so try removing it and see how that goes.
0
 
devsolnsCommented:
If that happens to be the issue an explaination will follow.
0
 
devsolnsCommented:
Since I wont be able to responde for a little while i'll give a little more. look at ApartmentState in general.  Components may need to run either Single threaded or mutlithreaded apartment.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now