Recording or replaying certain SAP transactions causes a spike in CPU or hang of the SAPGUI client
This is caused by a known issue in the SAPGUI when trying to load the complete SAPGUI hierarchy as it creates a very large load on the interface. Normally just a few fields are required for a test and it is not necessary to load the entire user interface.
You can work around the issue Silk Performer by disabling the additional logging:
1. Go to Settings | Active Profile | SAPGUI | Logging tab
2. Uncheck the “Log control information for single run in TrueLog” option for both record and replay (you can change between record and replay in the left hand window).
This workaround means you will lose the ability to customize the test using the wizard.
Note: This is a SAP issue rather than a Silk Performer one and affects all software vendors who use the SAPGUI scripting APIs for generating tests.