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
An earlier version of River5 seemed to have a memory leak: after running for months, the amount of free RAM dwindled, and the computer got slow. Stopping River5 (with Ctl-C) freed up the RAM, and the computer was much snappier. Starting River5 again (npm start) worked as expected. I'm not reporting a memory leak against an obsolete version...
But... this made me wonder if I was up to date. And I wasn't (I was using River5 v0.4.14). So I updated and had these observations with a git pull from 0c2804e on macOS 10.13.6:
The startup line shows [email protected], but later on, the log shows River5 v0.5.9 running on port 1337. This is confusing.
It would help with diagnostics if the startup information also displayed the date/time, and possibly the version of Node (I was using 5.3.0, which may also have been part of the memory leak problem.)
An earlier version of River5 seemed to have a memory leak: after running for months, the amount of free RAM dwindled, and the computer got slow. Stopping River5 (with Ctl-C) freed up the RAM, and the computer was much snappier. Starting River5 again (npm start) worked as expected. I'm not reporting a memory leak against an obsolete version...
But... this made me wonder if I was up to date. And I wasn't (I was using River5 v0.4.14). So I updated and had these observations with a
git pull
from 0c2804e on macOS 10.13.6:[email protected]
, but later on, the log showsRiver5 v0.5.9 running on port 1337.
This is confusing.Thanks!
The text was updated successfully, but these errors were encountered: