Anyone experiencing this same thing? It’s happened twice now, which is not a lot, but it’s odd that it’s happened twice.
I’ll go to start SD.Next and it will hang on Using VENV, the opening line. If I watch my RAM usage, it will ramp up to max before killing the process and startup will fail. I killed the venv folder and restarted, and the first time that didn’t solve anything. Only a complete reinstall of Vlad’s SD.Next worked for that.
The second time, just yesterday, it worked to reboot and rebuild venv. Anyone else experiencing this?
You must log in or register to comment.
SD.Next is doing the weirdest things from time to time. The startup script performs various
git pulloperations on every start so it autoupdates parts of itself, causing itself to break sometimes. Depending on your installed plugins it might execute code from the web. It does not upgrade itself automatically though.I recommend deactivating all autoupdate features and/or snapshotting your installation. (For example with an LVM thin volume mounted to its installation directory and snapshotting it before each start, this will also snapshot the python venv stuff).
The oddest thing is, it wouldn’t even get to the auto-update functions. Those are logged in the console, it was hanging on the very first logged line instead. The first time it happened, I thought it was some runaway recursion issue so I removed my symlinked folders, but neither that nor rebuilding venv fixed it.
Just curious if someone else has experienced it as well. I’m being more mindful of its autoupdate features now. I hope vlad implements a branching scheme soon before things get too out of hand.