We are running tests on Jenkins using KRE, suddenly tests stops for certain point of time but I am not getting why they are failing, I am not able to find where I can check the error too. and one more observation is that, it makes Jenkins stops when I run the Katalon tests on Jenkins after certain period of time
1 Like
kindly share info like screenshot or errors logs ? does ur test run more than 60mins? does the same tests running fine locally?
1 Like
Yes 500 test cases are running around 6 to 7 hrs of time
1 Like
Hi there,
Thank you very much for your topic. Please note that it may take a little while before a member of our community or from Katalon team responds to you.
Thanks!
kindly share the error logs? how your test case is configured?
its is configured sequentially
I am not able to upload image, log files here and there are no error logs found
Uploading: execution5.log…
Possibly you should allocate more memory to the JVM for KRE. You should edit the katalon.ini file.
I guess you got an “OutOfMemoryError” suddenly. It is a serious exception. When the system got that, it is quite likely that you get no logs because the system stops immediately without emitting logs into the ordinary log storages.
Where is katalon.ini? How should you edit the katalon.ini to allocate more memory?
Please ask that question to Katalon.
I was surprised to find that there is no official documentation how to configure -Xmx to JVM for Katalon Studio and KRE.
They should improve their documentation.
=> @Elly_Tran
Thank you, I am trying this solution
1 Like
I Tried with this solution but still test cases are struck
OpenJDK Platform binary has consumed 4707.5MB while running katalon test
Why I am not able to upload image, please let me know.
You once wrote that you got no error logs found.
How did you know that? If you got any log, could you share it here?
Your test consumed 4707.5MB? Really?
I think it is an extraordinarily large memory consumption for a Katalon project.
Years ago, I experienced a case where my Katalon project consumed over 4GB of JVM heap memory — and hanged. I debugged my Java code using VisualVM and found a bug. I fixed it. Then the memory consumption immediately dropped down under 512MB. The test suite got much more reliable, ran far faster.
What was the bug? One of my Java class loaded hundreds of PNG images one by one. But the class forgot to close the InputStream objects. Unclosed InputStream objects with large i/o buffers remained in the heap memory. They were left not garbage-collected. See StorageScanner is memory-leaking due to unclosed IO-buffers inside javax.imageio.ImageIO · Issue #20 · kazurayam/Materials · GitHub if you are interested.
My buggy test worked fine with a small amount of input data (1 or 2 PNG images as input). When I ran the test with hundreds of input data (600 PNG images), it got exploded and hang. The amount of data mattered.
I have a doubt that @deepaveerappa.kadrol’s code might have a memory-leak somewhere. But I am not sure. I guess so based on my experience.
Deadly slow, isn’t it? I am afraid, @deepaveerappa.kadrol’s code has some bugs that cause memory-leaks.
sure I will check one more time on the code, Thank you for the hint
6 to 7 hrs — too slow, I think.
Too much verbose messages in the LogViewer could slow down your tests in Katalon. Are you aware of that fact? Please have a look at the following post of mine.
did you check the code?
I went through this post, but it is explained more on KSE license based but I am getting issue for KRE and on Jenkins, I tried disable the Logs executable steps in settings but even though its struck for certain period of time. Now I am analyzing code as well to put some exception handling for failed test cases, I will update on the same, Thank you so much for the support
1 Like
Code works fine for normal scenario but if any failure happens its taking lot of time to execute that step, Its not coming out from that step faster.
Hint: I am running test suite sequentially
It took me a week to fix my memory-leaking program. So I suppose it would take @deepaveerappa.kadrol days and nights to identify the memory leak in their code.