wasm: fix "thread_in_wasm flag was not set" crash in debug builds.#16132
wasm: fix "thread_in_wasm flag was not set" crash in debug builds.#16132PiotrSikora wants to merge 6 commits intoenvoyproxy:mainfrom
Conversation
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
|
/retest |
|
Retrying Azure Pipelines: |
howardjohn
left a comment
There was a problem hiding this comment.
Its definitely possible I built it wrong as I had some difficulty, but I tested this and it seemed to have the same issue.
Thanks for testing! It's definitely possible that this PR doesn't fix the issue (I didn't replicate it locally yet), it's a cherry-pick of a fix that looked relevant, but perhaps there are even more issues around that code. I'll try to dig into it next week. |
|
OK, this indeed doesn't work. The failure can be easily replicated using: It passes on the CI, because it only uses I think it might be a false-positive, but I filled the issue with V8 team: |
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
|
@howardjohn if it's not too much trouble, could verify the updated version? It fixes the issue for me. |
|
@PiotrSikora I was able to test this and confirmed it addressed the issue |
…rapfix Signed-off-by: Piotr Sikora <piotrsikora@google.com>
|
@moderation I know that you're not a big fan of carrying patches, but debug builds are completely broken right now. Those patches will be removed once we update to V8 v9.2, but it won't happen until the end of next week when v9.2 is branched. |
|
Just like I'm not a fan of carrying patches, you are not a fan of putting a |
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
I've added TODO without a date or resolution, since there is nothing to do until the next version is branched and we update to it. I'm not a fan of adding TODO in this case, since patches are already clearly commented with the source of the cherry-picks, and adding it to the existing PRs triggers another multi-hour CI cycle, which in turn delays approval process and merge by another few days, while providing virtually zero value (historically speaking, I'm going be doing the update anyway). |
|
/retest |
|
Retrying Azure Pipelines: |
|
@moderation PTAL. |
|
/lgtm deps |
| # 2. Increase VSZ limit to 64 TiB (allows us to start up to 6,553 VMs). | ||
| # 3. Fix building and linking with MSAN. | ||
| # TODO(PiotrSikora): remove when not needed anymore (most likely in v9.2 branch): | ||
| # 4. Fix "thread_in_wasm flag was not set" crash in debug builds (https://chromium-review.googlesource.com/c/v8/v8/+/2817598, https://chromium-review.googlesource.com/c/v8/v8/+/2867468). |
There was a problem hiding this comment.
The changes listed are part of the diff below. LGTM!
antoniovicente
left a comment
There was a problem hiding this comment.
Anything to add @lizan ?
These changes LGTM.
@envoyproxy/senior-maintainers: would one of you want to take a look or should we merge this fix?
|
I merged v8 9.2, do we still need this? |
Nope. Thanks! |
Fixes istio/istio#30645.
Signed-off-by: Piotr Sikora piotrsikora@google.com