Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Issue: Internet Explorer memory error after log-off

Updated on February 16, 2006

Symptom

A developer asks: Has anyone seen a memory error upon logoff (to the effect of "...instruction at ZZZZZZ referenced memory at yyyyyyyy.  The memory could not be read.") ?  Do you know what may be causing it?

My users get this error when they click to log off. They see the "You have left" form. Then they click the X to close Internet Explorer and they see the error. They don't get this error any other time they use Internet Explorer or with any other Web applications.

The error occurs sporadically and they cannot reproduce it. There does not appear to be a consistent pattern for the time or circumstances under which this error occurs.

Solution

Explanation

Pegasystems has determined that this occurs due to conflict between one or more browser add-ons.  For a time, this error was completely reproducible after a workstation upgraded to Adobe Acrobat Reader 7, and disabling the AcroIEHlprObj add-in appeared to eliminate the problem. 

One theory is that one or more add-ons — not from Pegasystems — are not following the correct protocol for "hooking" key-press events, and do not correctly restore values when they are unloaded.

During 2005 , Pegasystems updated the Process Commander ActiveX controls to reduce the need to hook these events.  As a result, this message appears only rarely.

If you have a reproducible scenario, you can disable add-ons using Tools > Manage Add-ons to attempt to identify one add-on that seems to be causing the conflict.

 

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us