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. Visual Basic
  4. Error while loading a win form.

Error while loading a win form.

Scheduled Pinned Locked Moved Visual Basic
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.
  • J Offline
    J Offline
    John L Ponratnam
    wrote on last edited by
    #1

    When I run the windows application, sometimes I get such error message "The CLR has been unable to transition from COM context 0x1a6fd8 to COM context 0x1a6e68 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." Can I know why such error message we get?

    Regards, John.L.Ponratnam

    J 1 Reply Last reply
    0
    • J John L Ponratnam

      When I run the windows application, sometimes I get such error message "The CLR has been unable to transition from COM context 0x1a6fd8 to COM context 0x1a6e68 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." Can I know why such error message we get?

      Regards, John.L.Ponratnam

      J Offline
      J Offline
      Jon_Boy
      wrote on last edited by
      #2

      You may have a long running process in which .Net displays a error from the debugging assistants. Press CTRL+ALT+E to open the Exception options. I think this error is the Managed Debugging Assistants - ContextSwitchDeadlock. Try unchecking that setting and retrying the app. Did this work for you?

      Any suggestions, ideas, or 'constructive criticism' are always welcome. "There's no such thing as a stupid question, only stupid people." - Mr. Garrison

      modified on Tuesday, November 11, 2008 7:57 AM

      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