Dear all,
There are so many Java™ process when using UiPath. Is there any method to solve it?
Hi @jackie.yue
You can try adjusting the Java™ settings to optimize its performance. This can include increasing the heap size or adjusting the garbage collection settings. You can also try using a more recent version of Java™ if you are not already doing so.
Thanks!!
@jackie.yue are you specifically working on a Java technology based automation? if yes let me know so that we can related to why so many threads are running or even if they are related to UiPath and not some other process running in your machine
No additional process is spawned when interacting with a Java application. Everything happens inside the existing JVM.
If you are using the Use Application app card to start the application, maybe the top-level selector/app title from the card doesn’t match the state of the existing application and it always opens a new one.
Thanks Valad, I think the process mainly caused by using the Use Application app card. But how to avoid it?
Check the Open
property. It may be set to open a new app every time the card gets executed. Also, if the property is set to IfNotOpen
and you have the Match exact title
property set to true, then if will open a new instance of the app if the title is not fully matched with one of the existing instances.
Thanks all.
The problem has been solved by adding an process of “kill process”.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.