Relax external MAX_WASM_MEMORIES check for imported memory count about wasm-tools

[alexcrichton]

Ok thanks! I think #1390 should fix that case then, and I can do a version bump once that's ready.

[alexcrichton]

Yes I think this is definitely a bug in the validator where you probably don't have 81 linear memories but 81 aliases to the same linear memory. Do you have an example component you could share? I can reproduce this with:

(component
  (core module $m
    (memory (export "m") 1)
  )
  (core instance $i (instantiate $m))
  (alias core export $i "m" (core memory))
  ;; ... repeat that 100 times ...
  (alias core export $i "m" (core memory))
)

But I'd also like to confirm with a concrete component you have which doesn't validate if possible too

[chrisdickinson]

Sure – here's a link to a component containing a number of python native packages. I ran into the problem when I added pandas to the component; componentize-py fails to generate an output component due to the wasmencoder error:

Traceback (most recent call last):
  File "/Users/chris/projects/dylibso/li/demo/venv/bin/componentize-py", line 8, in <module>
    sys.exit(script())
             ^^^^^^^^
AssertionError: failed to validate component output

Caused by:
    memories count exceeds limit of 100 (at offset 0xebe202a)

(If you need the source to recreate the component, let me know – I've got kind of a mess of submodules set up for testing but can look into cleaning it up if that's helpful. 😅 )