You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 1, 2022. It is now read-only.
Intermittently, I'll find that the radicle-proxy process is eating upwards of 100% CPU and sometimes it reads near 1000% CPU in activity monitor. This is typically accompanied by my Macbook Pro feeling extremely hot and the fans running at full blast.
I have seen this on Radicle Upstream versions 0.2.4 and 0.2.6. I'm running MacOS Mojave 10.14.6.
Typically I observe this while Radicle Upstream has been on in the background for some time, though I have also observed it not very long after restarting the Radicle Upsream client.
The text was updated successfully, but these errors were encountered:
Thanks for creating this issue @Zerim. You’re not the first one reporting this and we are looking into it. Could you tell us what seeds you are connected to? You can find this information on the settings screen. It would also be helpful if you could start Upstream from the command line and save the log output.
Thanks for following up! I'll definitely give 0.2.7.8 a try, but I won't have a chance until the week after next. So will get back to you then.
In the meantime, here is a video of some of the logs I'm seeing from Radicle while its CPU usage was around 600-800%. Logs were moving too fast to easily copy/paste so I just screen recorded.
Intermittently, I'll find that the
radicle-proxy
process is eating upwards of 100% CPU and sometimes it reads near 1000% CPU in activity monitor. This is typically accompanied by my Macbook Pro feeling extremely hot and the fans running at full blast.I have seen this on Radicle Upstream versions 0.2.4 and 0.2.6. I'm running MacOS Mojave 10.14.6.
Typically I observe this while Radicle Upstream has been on in the background for some time, though I have also observed it not very long after restarting the Radicle Upsream client.
The text was updated successfully, but these errors were encountered: