Hi Prithviraj !
A memory leak in ServiceNow usually means some scripts or processes are holding onto memory longer than needed, which can slow down performance or cause instability. It doesn’t mean the platform itself leaks memory like low-level systems, but poorly written scripts can “behave” like a leak.
Common causes:
Inefficient GlideRecord queries inside large loops.
Global variables that never go out of scope.
Building very large strings or objects without clearing them.
How to prevent/handle:
Optimize GlideRecord queries and only fetch fields you need.
Always use var to declare variables inside functions (so memory can be released).
For large data processing, split jobs into smaller batches.
Use gr.next() properly in while loops and avoid using getRowCount() on big tables.
Regularly review Business Rules, Script Includes, and Scheduled Jobs for such issues.
Following these best practices helps keep memory usage under control and avoids performance problems.
Hope this helps!
Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it helpful & accept the solution so others can benefit as well.
