Many of you would’ve faced below errors during load testing using LoadRunner.
Action(24): Error -27977: Memory block size (65537) requested for value (<INPUT>) exceeds limit of 65535 bytes [MsgId: MERR-27977] Action(24): Error -27999: Not enough memory (65537 bytes) for a memory block for value (<INPUT>) [MsgId: MERR-27999]
Assume that you are working on HTTP/HTML protocol and you faced above errors. In this blog post we will see about how to rectify above errors and memory management in LoadRunner.
For memory related errors, the culprit should be hiding in advance run-time settings. To access go to Vuser > Run-Time Settings > Internet Protocol > Preferences > Options.
Scroll down to Web (Click and Script) Specific > Memory Management as shown below.
There are four parameters available such as follows:
- Default block size for DOM memory allocations.
- Memory Manager for dynamically-created DOM objects
Default block size for DOM memory allocations
By default you have 16384 block size for DOM memory allocations. If the value is too small then you might face extra calls to malloc which slows your execution. If the value is too big, it leads to larger footprint.
Memory Manager for dynamically-created DOM objects
If the choice is Yes then LoadRunner uses the memory manager for dynamically created DOM objects. If the choice is No, then it will not use. Use the protocol recommended choice.
Don’t want to miss any posts?
- Brotli Compression in Performance Testing - October 6, 2017
- Unboxing HPE StormRunner 2.7 - September 27, 2017
- What’s new in Apache JMeter 3.3? - September 25, 2017
- Measuring Client-side performance using Performance APIs - September 19, 2017
- Unboxing HPE LoadRunner 12.55 - August 20, 2017