valory-xyz / olas-operate-app

Apache License 2.0
0 stars 0 forks source link

Multiplication of Tendermint processes #214

Open oaksprout opened 4 days ago

oaksprout commented 4 days ago

Version: rc61 + rc60

Multiple users have reported that when they leave the app on for extended periods of time, it continuously spawns tendermint processes. This ends up taking up a significant and problematic amount of CPU resources.

image

dagacha commented 4 days ago

When opening Pearl after the app being not running and subsequently starting the agent this is what I see image

If leave Pearl running, close the lid of the laptop, and re-open it after a few mins, nothing changes. I've repeated the process 3 times.

If I pause the agent using Pearl's UI, and re-start it, a new tendermint process appears:

image

If I repeat the latter, new tendermint processes appear

image

cc @jmoreira-valory

dagacha commented 4 days ago

On top of that, closing Pearl does not kill the process aea_bin

Closing subsequently killing the process aea_bin doesn't kill the tendermint processes.

Finally I can stop the tendermint processes by killing them directly.

image
oaksprout commented 4 days ago

I've also noted that when I close the app, several tendermint processes remain running.

image

Same for aea_bin

image
dagacha commented 3 days ago

Different behavoiur observed: Pearl running in the background, laptop lid closed for 5-6hs, when opening laptop back lots of tendermint processes running. This time I did not pause / restart agent.

image
oaksprout commented 3 days ago

@solarw can you reference your branch with the fix here?

oaksprout commented 2 days ago

Potentially solved by: https://github.com/valory-xyz/olas-operate-app/pull/216

oaksprout commented 2 days ago

Testing #216 with all tendermint and aea_bin processes killed via rc64.

No new tendermint or aea processes spawned when I simply open and log in to the app.

After successfully starting the agent:

When I stop the agent:

After stopping the agent, I am able to successfully start the agent. In this case:

Now I fully quit the app whilst the agent is still running:

I reopen the app and log in successfully.

I successfully restart the agent:

oaksprout commented 2 days ago

I also tested leaving the app and agent running whilst I put my Mac to sleep – closed the lid.

When I re-opened the computer, the processes remain consistent.

After re-opening, I stop the agent and the processes are all killed, as expected.