In rare situations, some user interface actions done on PDF files might cause out of JAVA heap memory state, which would result in a slow or unresponsive system for users. This might happen for unique PDF files under these circumstances:

• Uploading the file directly to the Repository
• Uploading the file to Workspace and then checking the file in to the Repository
• From the Repository checking out the file into the Workspace and then checking the file back into the Repository
• Copying and pasting the file in the Repository
• Cutting and pasting the file in the Repository
• Deleting the file from the Repository

The following SAS^® Drug Development API Macro calls could cause similar issues when performing like actions as those listed above on a problematic PDF file:

• sasdrugdev_upload.sas
• sasdrugdev_copy.sas
• sasdrugdev_move.sas
• sasdrugdev_delete.sas

The workaround if this happens is to restart SAS^® Drug Development.

To obtain a fix for this issue, contact SAS Technical Support.

Operating System and Release Information