Problem Note 10956: Memory is not freed when terminating all objects in a Work Area
In SAS/AF Software, memory may not be freed when programmatically
terminating all objects in a work area object. If the work area object
is then populated again with new controls and the FRAME entry is not
terminated, the memory usage may go up. If this process of populating
and terminating the work area object is performed over and over, the
leak may grow to a substantial amount of memory.
The only circumvention is to open a new FRAME entry with the new work
area object in it after closing the previous FRAME entry so that memory
is freed.
A Technical Support hot fix for Release 8.2 (TS2M0) for this
issue is available at:
http://www.sas.com/techsup/download/hotfix/82_sbcs_prod_list.html#010956
For customers running SAS with Asian Language Support (DBCS), this
hot fix should be downloaded from:
http://www.sas.com/techsup/download/hotfix/82_dbcs_prod_list.html#010956
Operating System and Release Information
| SAS System | SAS/AF | Microsoft Windows XP Professional | 8.2 TS2M0 | 9.1 TS1M0 |
| Microsoft Windows NT Workstation | 8.2 TS2M0 | 9.1 TS1M0 |
| Microsoft Windows 95/98 | 8.2 TS2M0 | |
| Microsoft Windows Server 2003 Standard Edition | 8.2 TS2M0 | 9.1 TS1M0 |
| Microsoft Windows Server 2003 Enterprise Edition | 8.2 TS2M0 | 9.1 TS1M0 |
| Microsoft Windows Server 2003 Datacenter Edition | 8.2 TS2M0 | 9.1 TS1M0 |
| Microsoft Windows 2000 Server | 8.2 TS2M0 | 9.1 TS1M0 |
| Microsoft Windows 2000 Advanced Server | 8.2 TS2M0 | 9.1 TS1M0 |
| Microsoft Windows 2000 Datacenter Server | 8.2 TS2M0 | 9.1 TS1M0 |
| Microsoft Windows 2000 Professional | 8.2 TS2M0 | 9.1 TS1M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2003-10-22 11:10:40 |
| Date Created: | 2003-09-29 16:29:30 |
