Bitburner 1.4.0 - phonix.js requires 8.5gb ram :(

[lsv]

In a TOTAL new instance - run phoenix.js can not run on home, because it requires 8.5gb ram.

// kill all non-phoenix files on boot
     servers.map(server => server.pids).flat()
        .filter(process => process.filename != "phoenix.js" && process.filename != "sbin.keepalive.js")
        .forEach(process => ns.kill(process.pid));

If this is removed, it will be at 8.0gb ram usage, but then there is not enough ram to run sbin.keepalive.js.

Also it tries to run something on the lowest server, but with 0 threads - and thats an exception.

disableLog: Disabled logging for scan
exec: Cannot run script 'sbin.keepalive.js' (t=1) on 'home' because there is not enough available RAM!
keepalive not found
exec: Could not find script 'bin.gr.loop.js' on 'n00dles'
sleep: Sleeping for 100 milliseconds
exec: Could not find script 'bin.wk.loop.js' on 'n00dles'
sleep: Sleeping for 100 milliseconds
exec: Could not find script 'bin.gr.loop.js' on 'foodnstuff'
sleep: Sleeping for 100 milliseconds
exec: Invalid thread count. Must be numeric and > 0, is 0
Script crashed with runtime error

Ill see what happens when I get a million to upgrade the home ram :)

[trhr]

Good report. I think I solved the second problem already; was just a left-over remnant from before i branched dev off from main.

But that's definitely not the only instance of ns.kill() in the entire package. I'm more likely to remove ns.killall, because I've been transitioning to a pid-based decision tree. I'll think about it.

[trhr]

If you're trying to get under 8GB, a way better option is to comment out the hwgw import from lib.gamestates.so.js

That uses two gigs by itself on two lazy-funcs grow-analyze and hackanalyze, and at 8G, you're not running HWGW workloads anyway. That said, I'm not really targeting a completely fresh install. After your home bitnode, you always start with 32GB, so arbitrarily removing appendages of the script to support 8G seems silly.