Freeze when activating request/response headers

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Empty your IE cache
2. Open AppControl project 
3. Comment out "asynch and synch" notifications in form1.cs
4. Launch AppControl
5. Enter url http://www.nrj.fr/music

What is the expected output? What do you see instead?
AppControl freeze

What are the OS and IE versions?
Windows XP SP3, IE 7

What version of the product are you using?
Version 2.0.0.1

Please provide any additional information below.

I first noticed the issue in version 1.0.0.7.

Original issue reported on code.google.com by claire.a...@gmail.com on 26 Jun 2008 at 8:32

[GoogleCodeExporter]

Thank you. There are two reasons for the freeze. One is related to 
DocumentComplete's
URL parameter being null which can easily be remedied by adding a check, second 
is
related to the APP part which I am still investigating. All seems to be related 
to
the way this site uses javascript. This issue should be resolved in the next 
update.

Regards,

MH

Original comment by mehr...@gmail.com on 28 Jun 2008 at 9:30

• Changed state: Started

[GoogleCodeExporter]

Thank you for your answer :) I'll try to investigate the APP part too, please 
let me
know if you find a solution.

Claire

Original comment by claire.a...@gmail.com on 3 Jul 2008 at 10:38

[GoogleCodeExporter]

Hi,

I have found the cause of the issue in the ComUtilities component. To fix it, 
you 
need to comment out this part:

    //if( (pProtocolData->grfFlags & PD_FORCE_SWITCH) == 0)
    //  pProtocolData->grfFlags |= PD_FORCE_SWITCH;

in the CManagedAppBridgeSink::Switch method located in ManagedAppBridge.cpp 
file and 
Rebuild the solution.

Apparently, forcing a switch to the main thread while executing a synch 
operation, 
in certain conditions, can cause the application to hang.

Please note that now, in ProtocolHandlerOnResponse event, you will receive a 
System.InvalidOperationException (Cross-thread operation not valid: 
Control 'sometextbox' accessed from a thread other than the thread it was 
created on.
) if you attempt to display any values contained in 
ProtocolHandlerOnResponseEventArgs parameters in a text box. This can be 
remedied by 
using a combination of InvokeRequired and Invoke technique.

Regards,

MH

Original comment by mehr...@gmail.com on 13 Jul 2008 at 12:00

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

It works fine for me :)

I'm not sure I understand what you mean by "displaying any values contained in 
ProtocolHandlerOnResponseEventArgs parameters in a text box" : I do access 
values
contained in ProtocolHandlerOnResponseEventArgs and display them in the
"frmRequestResponseHeader" form with no exception thrown ...

With thanks,

Claire

Original comment by claire.a...@gmail.com on 16 Jul 2008 at 2:39