Uh oh!
There was an error while loading. Please reload this page.
[browser][MT] fix stale memory on suspended thread - #94299
Conversation
ghost
commented
Nov 2, 2023
Tagging subscribers to 'arch-wasm': @lewing Issue Detailstesting alternative to #90771 Problem: when WebWorker is suspended in the browser, the other running threads could We believe that described problem is cause of MT problems with debugger tests, example log
|
pavelsavara
commented
Nov 2, 2023
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
pavelsavara
commented
Nov 2, 2023
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
ec0a5ca to
aaed9b6Comparepavelsavara
commented
Nov 2, 2023
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Uh oh!
There was an error while loading. Please reload this page.
pavelsavara
commented
Nov 3, 2023
@thaystg I will wait for your feedback/approval |
pavelsavara
commented
Nov 3, 2023
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
pavelsavara
commented
Nov 3, 2023
Hmm, so now all errors are @thaystg does that mean my fix didn't help ? Or it means there is another issue ? Is debugger making the app to download something ? Does suspending thread while fetching break the fetch ? |
thaystg
commented
Nov 3, 2023
I also remember to have already tried it and it didn't help. But for me it's okay to try again. :) |
pavelsavara
commented
Nov 6, 2023
Where is "there" ? More details would help.
Could you please elaborate on what you tried ? |
4cb31ff to
6ebae17Comparethaystg
commented
Nov 6, 2023
Look at artifacts tab here: https://dev.azure.com/dnceng-public/public/_build/results?buildId=459235&view=ms.vss-test-web.build-test-results-tab&runId=10361536&resultId=100252&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab |
thaystg
commented
Nov 6, 2023
Unfortunately I don't remember details of what I tested, I tried a lot of things before the workaround in that PR. |
pavelsavara
commented
Nov 6, 2023
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
pavelsavara
commented
Nov 6, 2023
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
pavelsavara
commented
Nov 6, 2023
pavelsavara
commented
Nov 6, 2023
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
pavelsavara
commented
Nov 6, 2023
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
pavelsavara
commented
Nov 6, 2023
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
pavelsavara
commented
Nov 7, 2023
I think that the fix for memory views is good. Solid 10/10 There are problems with #89409 but that's unrelated issue |
thaystg
commented
Nov 7, 2023
@pavelsavara thanks a lot and congrats for this fix!!! |





Alternative to #90771
Problem: when WebWorker is suspended in the browser, the other running threads could
growthe linear memory in the meantime. After the thread is un-suspended it may to try to de-reference pointer which is beyond it's known view. This is likely V8 bug.We believe that described problem is cause of MT problems with debugger tests, example log