[browser][MT] stop doing grow(0)

[pavelsavara]

see what breaks

[dotnet-policy-service]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

[pavelsavara]

This is why we need grow(0)

Log

[18:06:20] info: Assembly: System.Reflection.Context.Tests, Version=9.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51 (System.Reflection.Context.Tests.dll)
[18:06:20] fail: [worker-idle 18:06:20.491] MONO_WASM: Unhandled error: RangeError: Invalid atomic access index
[18:06:20] fail: [worker-idle 18:06:20.574] MONO_WASM: Invalid atomic access index
                 RangeError: Invalid atomic access index
                     at Atomics.waitAsync (<anonymous>)
                     at Object.__emscripten_thread_mailbox_await (http://127.0.0.1:41991/_framework/dotnet.native.js:8:102771)
                     at handleMessage (http://127.0.0.1:41991/_framework/dotnet.native.worker.js:1:2103)

I will keep this PR until we could also test in on FF
And also I would be interested to see if latest emscripten has the same issue

cc @kg @radekdoulik

[pavelsavara]

Here is firefox version of the same problem Log

JavaScript error: http://127.0.0.1:36241/_framework/dotnet.native.wasm, line 157841: RuntimeError: index out of bounds

grow(0) helps with it on firefox too. Is that strange ?
cc @kg

[dotnet-policy-service]

Draft Pull Request was automatically closed for 30 days of inactivity. Please let us know if you'd like to reopen it.