Same Issue was already reported by @sonyvec. However the solution was not working.
Could some one help us in why this error is happening? how to solve this.
I solved this by increasing max-old-size to 2048 and expanding my swap partition to 2gb (which should sum up to 2.5gb total ram on my raspberry, where .5gb are actual ram and 2 are swap).
If you can modify your swap on the go, remember to reboot your server
I’ve been trying to tackle this issue for quite some time. Usually adding some swap space helps, but it doesn’t guarantee anything. My PR to update Node’s memory usage dynamically by checking the availability before running rollup didn’t go anywhere.
So I’ve written a new feature which builds and maintains assets. This only works on develop and the next v13-beta. However, this feature enables assets to be packaged and attached to the GitHub releases that will be made henceforth. If you can craft an alternative script to utilize those assets instead of having to build on your servers.
Also, if you’re comfortable with docker, Frappe Docker could also work for you.