Katalon Studio hangs when double-clicked on the Dictionary Property Builder for Desired Capabilities

Bug Report
1

I made a GitHub repository of the project that you can reproduce the issue:

I used Katalon Studio v１０.３.2 free on macOS 15.2.6

I opend the dialog Project > Settings
I navigated to Desired Capabilitites > Web UI > Chrome
I chose the Value of prefs.
Then a diaglog titled “Dictionary Property Builder” opend.
I chose the 1st row of “download.default_directory”, then the row’s background color turned to be blue.
I gave double click on the Value field of the row; I intended to edit the value from ‘/Users/kazurakiurayama/tmp’ to /Users/kazurayam/tmp;

501350160-216ed591-e93f-43ba-bb2c-23269f2d7da2
501350160-216ed591-e93f-43ba-bb2c-23269f2d7da21522×1042 133 KB

I did a double click over the Value string /Users/kazurayam/tmp; Katalon Studio did not respond to the click at all.
I did a double click again — still not responding.
I repeated double clicking a few times.

I felt that the poor Katalon Studio was working too slow; it could not catch up with my finger operations

Katalon Studio hanged in the end. A spinning wheel icon of macOS appeared and never stopped.

macos-wait-cursor

I couldn’t do anything on Katalon Studio. I wanted to edit the property value but I couldn’t. So, I terminated the Katalon Studio window by the OS level operation.

/Applications/Katalon Studio.app/Contents/MacOS/config/.metadata/.log is here:

.log

This issue is easily reproducible. If you try the same procedure, you will see the spinning wheel.

I did this exercise on Mac only. I didn’t check this on Windows.

To @nghi.phan

Please pass this to the Katalon developers.

2 Likes
2

Dear Mr Kazu,

Since this is a known issue, I have passed this also to our team, stay tune for updates from us. Thank you for raising this up.

3

Was it known to Katalon? How long has Katalon left this issue unaddressed? Is it negligible for you?

1 Like
4

I completely understand your concern, it’s a valid question. Our team is aware of the issue, and the engineering team is actively investigating it to determine the root cause. It’s definitely not being treated as negligible :smiling_face_with_tear:. I’ll make sure to update you as soon as we have more clarity from the investigation.

Thank you for your patience and for continuing to bring these details to our attention :star_struck: