(In reply to Tooru Fujisawa [:arai] from comment #1) > does it help if we have debug-only and chrome-only assertion for checking if there's a promise reaction job in a dying global where the promise reaction job is for different global? > or will it hit frequently outside of the problematic case? Yes, it would help to have some debugging tool to get a stack or something that allows us to recognize the stalled code. I can't tell how frequently it would hit, but it can surely hit both users and tests. So, it would be nice to have something we can enable on demand and run tests locally on on Try with it.
Bug 1857882 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Tooru Fujisawa [:arai] from comment #1) > does it help if we have debug-only and chrome-only assertion for checking if there's a promise reaction job in a dying global where the promise reaction job is for different global? > or will it hit frequently outside of the problematic case? Yes, it would help to have some debugging tool to get a stack or something that allows us to recognize the stalled code. I can't tell how frequently it would hit, but it can surely hit both users and tests. So, it would be nice to have something we can enable on demand and run tests locally or on Try with it.