It's quite unlikely that Intersoft controls could cause such "hang" issue as we never experienced one before.

If you used IE 8, you can try to use Developer Tools and start Javascript debugging. Then, click on the "Pause" button which will then stop at the point where the IE executes the code. You can use this technique when the IE consumes about 50% of CPU, and it will tell you exactly which line of code that executes the program.

Please let me know if you can find anything on this issue. Thanks!

Hope this helps,
James.

Hi,

The browser we use for our app is IE7.  In trying to diagnose this problem I've used Visual Studio to debug server and client side code, and each time an IE hang occurs there is no code being hit. 

Currently I'm at a loss as to why this happens.

Hi Adrian,

Yes, it'll be difficult to put a breakpoint on the code that caused the IE to hang. If you don't have IE Developer Tools, you can use Visual Studio to detect the problematic code. Here's how:

• Run your webform in debugging mode, this should launch IE with the process attached to Visual Studio debug mode.
• Perform some actions or wait until the IE seems hang, then quickly click "Pause" button in Visual Studio (the button is located in the Debugging toolbar).
• When you got the right moment, IE will pause and show you what code that it currently executes. That code will likely be the cause of the IE hang.

Hope this helps,
James.

Ditto for me also.  I've been experiencing the same issue with WebPaneManager.  It seems that if you get too many nested instances of this control going the browser will hang.  If you look at Task Manager during the hang the browser hogs an enormous amount of CPU %.  Sometimes, if you wait long enough, the browser will finally finish whatever it is that it is doing and then allow you to interact with the page.  Sometimes; however, it never returns and you finally have to kill your session.  I had debugged into this a while back and found that it seemed to hang inside of one of Intersoft's obfuscated javascript functions.  I had no idea what the function did, obviously, but it was definitely inside of an Intersoft function.  I had to move on to some other fires at the time but I'm now needing to get this addressed.  I'm going to see if I can find the name of that function again and then post it here.  I'm glad to see that someone else has experienced the same thing.  I thought I might be going crazy.

Jerry

Yep,

I never managed to resolve this issue and my work around was to remove the WebPaneManager from the page and use standard HTML tables to control the layout.

I trying debugging the issue with everything in my arsenal but to no avail, I set breakpoints everywhere in the JavaScript code and none of them ever fired so I assume it must be something internal to the Intersoft JavaScript.

Regards,

Adrian.

Do you mind creating a simple sample that will create the issue? Or perhaps explain in more details regarding the WebPaneManager structure you are using to cause the issue.

I redesigned the page using HTML tables rather than the WebPaneManger which seems to have fixed the problem.

However since I've upgraded to WebUI Studio 2009 I am getting random IE "hangs" on other pages previously unaffected.

Adrian, do you mind explaining the other page structure that will cause the issue?

I've been experiencing the same issue withWebPaneManager. It seems that if you get too many nestedinstances of this control going the browser will hang. ... I had debugged into this a while back and found that it seemed to hang inside of one of Intersoft's obfuscated javascript functions. ... I'm going to see if I can find the name of that function again and then post it here.

Jerry, thank you in advance for the effort, however in the mean time, which nested instance do you meant? perhaps you could send us the WebPane structure you are using?

Having the WebPane page / structure that cause the issue will help us in recreating the issue in our environment and determine the cause of the issue quicker.

We are using a structure with multiple levels of nested master pages.  It would be pretty difficult for me to re-create a sample to send that would simulate what I’m experiencing.   Suffice it to say that we have WebPaneManagers at each level of the master pages that break the screen real estate into more granular containers. 

Our main master page has this layout:

+-----------------------------+

| Caption                     |

+---------------------+-------+

|                     |   L   |

|                     |   I   |

|         Content     |   N   |  

|                     |   K   |

|                     |   S   |

+---------------------+-------+

We then have what we call a Profile Master Page that nests inside of the Main Master page’s content area.  Its layout is as follows:

+-----------------------------+

| Sub-Caption                 |

+-----------------------------+

| Page Menu                   |

+-----------------------------+

| Tab Control with mult. Tabs |

+-----------------------------+

| Menu specific to sel. Tab   |

+-----------------------------+

| Content                     |

|                             |

|                             |

|                             |

|                             |

+---------------------+-------+

The final master page nests inside of the content area of the Profile Master Page and is laid out as follows:

+-----------------------------+

| Caption                     |

+--------------+--------------+

| Microsoft    |  Pane with   |

| Templated    |  info        |

| GridView     |  specific    |

| Control      |  to          |

|              |  selected    |

|              |  grid row    |

|              |              |

|              |              |

+--------------+--------------+

The WebPaneManager control seems to work quite well in most of the areas of our application; however, the couple of pages I'm having difficulty with have Microsoft Templated GridView controls in the WebPanes.  When the "Edit" link in these grids is clicked the postback occurs as expected and you can debug completely through the C# code to the point where control is handed back to the browser.  It is at that point that IE goes into some sort of infinite loop that occasionally recovers.  On those occasions where IE does recover it takes approximately 60 seconds for the loop to terminate and the browser to return to a normal state. 

I backward tested the same code with the 2008 Intersoft Suite and those problematic pages work flawlessly.  These are all relatively mature pages that worked great on the prior release.  We caught this strange behavior during regression testing after the 2009 upgrade.  I’m assuming that some sort of change crept into the latest Intersoft release that is causing the issue.

Would it be possible for me to use the 2008 WebDesktop assemblies and JavaScript files in conjunction with the newer assemblies for the other modules (e.g. WebGrid, WebInput, etc.) until this issue is resolved?  Or would there be some incompatibilities?

Thanks in advance,

Jerry

Using resources (javascript files) from previous build with thecomponent dll latest build is not suggested. The component dll may refer to newly created function that was not available in the previous javascript build.