Usage Note 41571: SAS® Data Integration Studio 4.2 might become unresponsive after heavy usage
After heavy or prolonged use of SAS Data Integration Studio 4.2, the user interface might become sluggish and ultimately unresponsive. Closing and re-opening SAS Data Integration Studio usually restores performance.
To work around this issue, modify the SAS Data Integration Studio client properties file, distudio.ini, and adjust the Java memory settings.
Perform these steps to implement the necessary changes:
- Navigate to the SAS Data Integration Studio installation folder on your
client machine. The default installation location for the product is
C:\Program Files\SASHome\SASDataIntegrationStudio\4.2.
- Make a copy of the file distudio.ini and save it (without modification) as a backup file.
- Using a text editor, open the file distudio.ini.
- Modify the JavaArgs_1 parameter and increase the maximum Java heap size (-Xmx) from 512m (the default value) to 1024m. Here is how the line should appear after the update:
JavaArgs_1=-Xmx1024m
Caution: If you set the maximum Java heap size (-Xmx) to a value that exceeds the maximum available memory on your machine, the SAS Data Integration Studio client will not launch. If this occurs, edit the distudio.ini file and reduce the setting of this option until the client launches successfully.
- Add an additional JavaArgs parameter that sets a higher maximum value for Java permanent generation heap space (-XX:MaxPermSize). Here is how the line should appear after the update:
JavaArgs_13=-XX:MaxPermSize=128m
-
Save the distudio.ini file.
Operating System and Release Information
| SAS System | SAS Data Integration Studio | Windows 7 Ultimate x64 | 4.21_M2 | 4.3 | 9.2 TS2M3 | 9.3 TS1M0 |
| Windows 7 Ultimate 32 bit | 4.21_M2 | 4.3 | 9.2 TS2M3 | 9.3 TS1M0 |
| Windows 7 Professional x64 | 4.21_M2 | 4.3 | 9.2 TS2M3 | 9.3 TS1M0 |
| Windows 7 Professional 32 bit | 4.21_M2 | 4.3 | 9.2 TS2M3 | 9.3 TS1M0 |
| Windows 7 Home Premium x64 | 4.21_M2 | 4.3 | 9.2 TS2M3 | 9.3 TS1M0 |
| Windows 7 Home Premium 32 bit | 4.21_M2 | 4.3 | 9.2 TS2M3 | 9.3 TS1M0 |
| Windows 7 Enterprise x64 | 4.21_M2 | 4.3 | 9.2 TS2M3 | 9.3 TS1M0 |
| Windows 7 Enterprise 32 bit | 4.21_M2 | 4.3 | 9.2 TS2M3 | 9.3 TS1M0 |
| Microsoft Windows XP Professional | 4.21_M2 | 4.3 | 9.2 TS2M3 | 9.3 TS1M0 |
| Microsoft Windows Server 2008 for x64 | 4.21_M2 | 4.3 | 9.2 TS2M3 | 9.3 TS1M0 |
| Microsoft Windows Server 2008 | 4.21_M2 | 4.3 | 9.2 TS2M3 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 for x64 | 4.21_M2 | 4.3 | 9.2 TS2M3 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Standard Edition | 4.21_M2 | 4.3 | 9.2 TS2M3 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Enterprise Edition | 4.21_M2 | 4.3 | 9.2 TS2M3 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Datacenter Edition | 4.21_M2 | 4.3 | 9.2 TS2M3 | 9.3 TS1M0 |
| Microsoft® Windows® for x64 | 4.21_M2 | 4.3 | 9.2 TS2M3 | 9.3 TS1M0 |
| Windows Vista | 4.21_M2 | 4.3 | 9.2 TS2M3 | 9.3 TS1M0 |
| Windows Vista for x64 | 4.21_M2 | 4.3 | 9.2 TS2M3 | 9.3 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.
| Date Modified: | 2015-06-04 15:22:27 |
| Date Created: | 2010-11-11 12:48:20 |
