Product Information
-
Product: Katalon Studio Enterprise
-
Version: 11.0.1
-
OS: Windows 64-bit
-
Project Type: Web UI Automation
-
TestOps: Enabled
Problem Statement (Critical)
After upgrading to Katalon Studio 11.0.1, the IDE consistently becomes completely unresponsive when switching the Execution Profile from default to any other profile.
This is a blocking issue that prevents further usage of the IDE.
Reproducibility
Reproduces 100% of the time
Does not require test execution
Triggered specifically by Execution Profile change
Steps to Reproduce
-
Launch Katalon Studio 11.0.1
-
Open an existing automation project
-
Attempt to change Execution Profile (e.g.,
default→QA/UAT)
Actual Behavior
-
IDE immediately goes into “Not Responding”
-
UI never recovers
-
JVM memory usage grows continuously (~1.4 GB and increasing)
-
Memory is not released, indicating a potential heap leak or GC deadlock
-
CPU usage remains low (not a busy loop)
-
Process must be force-killed via Task Manager
Expected Behavior
-
Profile switch should complete normally
-
IDE should remain responsive
-
Memory usage should stabilize or be reclaimed by GC
Regression Confirmation
This issue:
-
Does not occur in earlier Katalon versions on the same machine -
Started only after upgrading to version 11.0.1 -
Rolling back to an older version restores normal behavior
This clearly indicates a regression introduced in 11.0.1.
Additional Diagnostic Observation
Another team member working on the same project, started using Katalon Studio 11.0.1, have not faced this issue on a different machine/environment (USA).
They are able to switch profiles and execute tests successfully.
This suggests:
-
Environment‑dependent triggering
-
But still a product-level defect, as:
-
The same machine worked on previous versions
-
Failure is deterministic post-upgrade
-
The issue is isolated to a specific IDE operation
-
Impact
-
Execution profiles cannot be changed
-
Environment-based testing is blocked
-
IDE becomes unusable
-
This directly affects project deliverables
Severity: Critical / Productivity Blocker
Suspected Root Cause (for Engineering Review)
Based on observed behavior, this may be related to:
-
Execution Profile reloading logic
-
GlobalVariable re-initialization
-
Groovy script cache rebuild
-
TestOps background sync hooks
-
Plugins or listeners not being disposed
-
Heap objects remaining strongly referenced after profile switch
Workaround which is working for time being is to disable the testOps and then again enable the connection, but this cannot be a solution. Katalon team must provide solution



