Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C#
  4. What does this mean????

What does this mean????

Scheduled Pinned Locked Moved C#
performancehelpmobiledotnetcom
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    saud_a_k
    wrote on last edited by
    #1

    Managed Debugging Assistant 'ContextSwitchDeadlock' has detected a problem in 'D:\Project1\Project1\bin\Debug\Project1.vshost.exe'. Additional Information: The CLR has been unable to transition from COM context 0x1b1c30 to COM context 0x1b1da0 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 got this error...? Im scared:omg:

    _____________________________________________________ Yea! I could be wrong...

    C 1 Reply Last reply
    0
    • S saud_a_k

      Managed Debugging Assistant 'ContextSwitchDeadlock' has detected a problem in 'D:\Project1\Project1\bin\Debug\Project1.vshost.exe'. Additional Information: The CLR has been unable to transition from COM context 0x1b1c30 to COM context 0x1b1da0 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 got this error...? Im scared:omg:

      _____________________________________________________ Yea! I could be wrong...

      C Offline
      C Offline
      Christian Graus
      wrote on last edited by
      #2

      This[^] is how I deal with unusual errors.

      Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups