[wasm][debugger] Fix loading a non wasm page and then returning to a wasm page. #60688
Conversation
|
Tagging subscribers to this area: @thaystg Issue DetailsIt was creating a new store, but it was not creating a new SdbHelper nor cleaning the cache, now when I set the store on SdbHelper I clear the cache. I think we can open a PR to servicing, or maybe to 6.0? I don't think it's too risky.
|
radical
left a comment
radical
left a comment
There was a problem hiding this comment.
LGTM! Thanks for addressing the comments 👍
|
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsIt was creating a new store, but it was not creating a new SdbHelper nor cleaning the cache, now when I set the store on SdbHelper I clear the cache. I think we can open a PR to servicing, or maybe to 6.0? I don't think it's too risky.
|
|
@lewing will we backport it? |
|
/backport to release/6.0 |
|
Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/1373379841 |
ghost
locked as resolved and limited conversation to collaborators
4 participants
It was creating a new store, but it was not creating a new SdbHelper nor cleaning the cache, now when I set the store on SdbHelper I clear the cache.
Also don't throw an exception when have an error while trying to call the debugger functions (as it was done before moving to use debugger-agent).
I think we can open a PR to servicing, or maybe to 6.0? I don't think it's too risky.
Fixes #60613