SA-5634

Summary

After opening a case that is displayed through IAC, when attempting to close the browser, the browser hangs and CPU goes to 25-50% and never recovers.

PRPC 7.1.4
WAS 7
Oracle 11
IBM JDK 6
IE 10

This issue is consistently reproducable. This issue occurs in IE 8 and Firefox 27 also. In Firefox I get the following warning:
"Warning: Unresponsive script:
A script on this page may be busy or may have stopped responding. You can stop the script now, or continue to see if it will complete.
Script: http://ipaddress.customer/prweb/ADServlet/JrgdioIldbiYq....../pega_ui_harness_deferred_123..!!.js:17
Continue or Stop Script"

All connections use load balanced URLs

Error Messages

none
----------------------
This issue occurs in IE 8 and Firefox 27 also. In Firefox I get the following warning:
"Warning: Unresponsive script:
A script on this page may be busy or may have stopped responding. You can stop the script now, or continue to see if it will complete.
Script: http://ipaddress.customer/prweb/ADServlet/JrgdioIldbiYq....../pega_ui_harness_deferred_123..!!.js:17
Continue or Stop Script

Steps to Reproduce

open user portal
search for a case
open case
attempt to close browser

Root Cause

The "doExplorerFormIsDirty" method defined in "pzpega_ui_doc_dirtyhandling.js" contains the root cause of this issue.

A variable is being used without being declared, so in a situation where multiple nested iFrames are are used through FCM you can end up in a recursive loop.

The change required is to use the "var" keyword to declare a variable in the javascript. 

We changed following statement:

"for (i = 0; i < win.frames.length; i++)" 

to 

"for (var i = 0; i < win.frames.length; i++)"

in pzpega_ui_doc_dirtyhandling.js.

Resolution

This issue is resolved by hotfix item Hfix-20112.