Tracker for issues reported to the V8 team

[PiotrSikora]

Issues reported using V8 issue tracker:

• [ ] V8 Wasm performance unexpectedly low for emscripten micro benchmarks
• [X] Leaky read-only space caught with TCMalloc HEAPCHECK
• [X] Increase maximum number of Wasm modules per process
• [X] Increase maximum number of Wasm memories per process
• [ ] Increase maximum number of Wasm stores (V8 isolates) to more than 256
• [X] Serialized Wasm module cannot be deserialized and shared or serialized again in another process
• [X] Memory leak when using the Wasm C++ API (for https://github.com/istio/istio/issues/27671)
• [X] Bazel BUILD files for v8
• [X] "thread_in_wasm flag was not set" when using Wasm C/C++ API callbacks in debug builds
• [ ] Setting memory limit sometimes fail, with wasm_max_mem_pages set

[dio]

Perhaps we can add the following as well:

• [x] Setting memory limit sometimes fail, with wasm_max_mem_pages set (resolved: https://bugs.chromium.org/p/v8/issues/detail?id=13395#c3)

Thanks!

[dio]

https://github.com/proxy-wasm/proxy-wasm-cpp-host/issues/67#issuecomment-1283431608 is updated, and resolved: https://bugs.chromium.org/p/v8/issues/detail?id=13395#c3