E
esebastian
Hi All,
We have an infopath 2007 form that is being hosted in a windows c#
application. I have a lot of custom code that works with the
formcontrol mostly switching views and inserting nodes into the xml.
Once in a while the form actually stops responding and you can't use
the form at all. I can however continue to add nodes to the form xml
through my windows functionality and i can see that the nodes are
actually being added by becuase the form has stopped responding the
new nodes do not appear. Has anyone encountered this, does anyone know
what's happening?? I have been able to find a COM exception that i
think is related to the form not responding, here is the message:
ContextSwitchDeadlock was detected
Message: The CLR has been unable to transition from COM context
0x196df8 to COM context 0x196c88 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.
Thanks,
Erin
We have an infopath 2007 form that is being hosted in a windows c#
application. I have a lot of custom code that works with the
formcontrol mostly switching views and inserting nodes into the xml.
Once in a while the form actually stops responding and you can't use
the form at all. I can however continue to add nodes to the form xml
through my windows functionality and i can see that the nodes are
actually being added by becuase the form has stopped responding the
new nodes do not appear. Has anyone encountered this, does anyone know
what's happening?? I have been able to find a COM exception that i
think is related to the form not responding, here is the message:
ContextSwitchDeadlock was detected
Message: The CLR has been unable to transition from COM context
0x196df8 to COM context 0x196c88 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.
Thanks,
Erin