ReadyAPI 3.0.0 - The closing of projects takes a very, very long time

Question

Hello,there are two issues regarding the function close a project.&nbsp;With the new version of ReadyAPI 3.0.0 I can't close a project without saving.&nbsp;Second issue is, when I close a project with the option to save then&nbsp;the closing takes almost half an hour or more. Over the performance monitor from Windows 10 I can see that&nbsp;about 30% of the computing power is used. The RAM comsumation ist round about 800 MB and I have more then 10 GB RAM free. There are no activities on the SSD. I can see this effect too when I start the programm and I&nbsp;immediately close one project. It does not matter how big the project is.How can I accelerate the closing of a project?

tanyayatskovska · Accepted Answer

Hi&nbsp;giovanni_favara,
&nbsp;
Could you please install the latest maintenance build and check how it works for you? You can download it here:
https://support.smartbear.com/downloads/readyapi/maintenance
&nbsp;
Also, it makes sense to follow the recommendations given in the&nbsp;Optimizing Memory Usage&nbsp;article.

giovanni_favara · Answer

Hello&nbsp;TanyaYatskovska&nbsp;,with the new version it works one time well.&nbsp;Afterwards the program behaves like the official version. Sometimes I observed that the project was not only closed but also removed from the workspace in the snapshot.

tanyayatskovska · Answer

Hi&nbsp;giovanni_favara,
Thanks for checking this.&nbsp;The behavior sounds very strange. Could you please submit a case to our Support team along with the problematic project? They will need to investigate the issue in our test lab. You can contact the team here:&nbsp;https://support.smartbear.com/message/?prod=readyapi

felder71 · Answer

Did anything ever come of this? I have the same issue with my projects in ReadyAPI 3.0/3.1. It's actually a little interesting because with Ready API 2.x, they took a little bit to open but in 3.0/3.1, they open fast enough. But closing in 3.0/3.1 could take forever (if it actually works - sometimes it just crashes) and it was very quick in 2.x.

giovanni_favara · Answer

Hi&nbsp;Felder71&nbsp;,The support could not reproduce the problem. I have deleted my user settings and the workspace file. Afterwards the problem was solved for a certain time.&nbsp;With version 3.1 I have the problem that ReadyAPI takes very long to start - several minutes. Closing the application was sometimes faster, it is still acceptable.&nbsp;I think that both observations are related - only the effects have changed. While waiting, ReadyAPI uses 30% of the CPU. It does something but I don't know what.

felder71 · Answer

I appreciate the info. It's really frustrating and I'd think they would be able to figure out what it is churning on. The one thing that has definitely helped is breaking things down into smaller projects, but that has really wreaked havoc with Git. Oh well. Thanks!

Forum Discussion

ReadyAPI 3.0.0 - The closing of projects takes a very, very long time

6 Replies

Related Content

ReadyAPI is not closing jdbc connections

ReadyAPI and TestEngine with Zephyr Scale

ReadyAPI and TestEngine with Zephyr Scale

Runing a composite ReadyAPI project from Github Actions

ReadyAPI Update - Moved from 3.30.0 to 3.49.0 - Project Issues

Recent Discussions

MyFirstPlugin - button Project menu in Ready Api

Integrate ReadyApi with Devops Release pipelines

Is it possible to integrate the Azure TestPlan Test cases and the ReadyAPI tests ?

How to connect to Azure blob storage in Ready API

JDBC Request/Query for value located within data BLOB