Insufficient resources: could not allocate code memory about nearcore HOT 4 CLOSED

As the comment in the relevant code suggests, 8 is the best guess we made at the time. This works for neard as it can only have as many contracts running in parallel as there are shards being tracked by a node.

near-vm-runner is not written with any other use-cases in mind and I'm not sure what it would take before we consistently consider other users.

It wouldn’t be too hard to make the pool arguments configurable here. Add some fields to the Config struct & use those parameters to construct the pool. For neard the default values of these parameters should stay the same, but in your tests you would be able to specify whatever value you wish at the time you construct the runtime.

from nearcore.

near-vm-runner is not written with any other use-cases in mind and I'm not sure what it would take before we consistently consider other users.

But version 0.17.0 works fine. Unfortunately, this version doesn't support contracts compiled with recent Rust versions.

from nearcore.

That's unsurprising. The pool of memories has been added reasonably recently and having it be fixed size is actually desirable for neard as there have been concerns about statically establishing an memory requirement ceiling for the runtime.

The fact that a prior version worked for an external use-case doesn’t change the essence of my statement either. near-vm-runner is developed and maintained for its primary use as a runtime within the reference NEAR validator. Suitability for any other use-case is incidental.

That said, there's no reason it cannot be used elsewhere, but an implicit expectation is that the interested parties would contribute to the effort (of making it suitable for those other use-cases and helping to keep it in that shape by e.g. contributing to reviews.)

from nearcore.

Looks like the issue has been fixed in the near-vm-runner 0.20.0.

from nearcore.