Finally I have something technical to contribute. God dammit. So I’ve decided to embark on a journey of pushing software called
thelounge to it’s breaking point. I’m running it on a raspberry pi 4 with 4GB of RAM and little much else to do except placate me. I set it up to record
-1 lines of buffer and I’m connected to a bouncer that’s on multiple networks with a handful of channels on each network. Some are large volume channels with lots of comms.
I knew I’d run into this, but I’m finally experiencing some of the limits of the software. Lately my service has been restarting semi-randomly with a log error as such:
After a ton of googling, I found this command line switch for nodejs:
--max-old-space-size=8192. Thanks, StackExchange.
But how do I tie this into what I’m doing? Well, Systemd simply points to
/usr/bin/thelounge start in order to start the process. I opened the file with vim and saw that it’s just a typical script using
/usr/bin/env to execute nodejs for interpretation. I also found you can pass command line arguments with
env. So I edited the first line of my script just so:
thelounge I fired up good ‘ol
htop and was greeted with this:
Badass. It looks like slipping our little
env parameter into the binary worked. It’ll continue to work until
/usr/bin/thelounge gets overwritten by an upgrade.
2020-10-28 11:30 AM