Meteor update failing with Cannot enlarge memory arrays

help
1

trying to run meteor update --release 3.1 on a Meteor v2 project and getting the following error, any ideas?

MINISAT-out: Cannot enlarge memory arrays. Either (1) compile with -s TOTAL_MEMORY=X with X higher than the current value 67108864, (2) compile with ALLOW_MEMORY_GROWTH which adjusts the size at runtime but prevents some optimizations, or (3) set Module.TOTAL_MEMORY before the program runs.

MINISAT-err: Cannot enlarge memory arrays. Either (1) compile with -s TOTAL_MEMORY=X with X higher than the current value 67108864, (2) compile with ALLOW_MEMORY_GROWTH which adjusts the size at runtime but prevents some optimizations, or (3) set Module.TOTAL_MEMORY before the program runs.

I do see Trouble updating to 3.0-alpha.17 (minisat) but it seems stale

2

kinda hacked around this by temporarily reducing the number of packages in the meteor packages file

3

That worked for me, reduce number of packages and re-adding them without version constraints. Since then after the 3.0 update no more issues

1 Like
4

Hi @adamginsburg and @bratelefant, could you please help us out?

@nachocodoner has included a fix for this issue (i.e. updated minisat) in Meteor 3.2-beta.1 , which he’s just published.

Could you please verify that updating from your previous version now succeeds (e.g. updating from the same v2 project as per 24 December via meteor update --release 3.2-beta.1 in @adamginsburg’s case), and let us know?

2 Likes
5

We delivered a fix on this issue on Meteor 3.2.

To use it, run: meteor update --release 3.2 or meteor create --release 3.2.

Let us know if it is completely fixed for you.

1 Like
6

meteor update --release 3.2 does not work - still breaks with the same error during update - I guess staying at v2.16 for a while - I saw a very old stackoverflow question from @webmagnets from 2016 - I wonder how this was resolved?
Thanks