Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upFix unloading, active BC, and clearing js runtime #24789
Conversation
highfive
commented
Nov 20, 2019
|
Heads up! This PR modifies the following files:
|
highfive
commented
Nov 20, 2019
|
@bors-servo try=wpt |
fix unloading, active BC, and clearing js runtime <!-- Please describe your changes on the following line: --> Move the unload steps of the currently active doc to the beginning of the "load" for the new document. Only nullify the window proxy if it's not used by another window. --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: --> - [ ] `./mach build -d` does not report any errors - [ ] `./mach test-tidy` does not report any errors - [ ] These changes fix #24591 (GitHub issue number if applicable) <!-- Either: --> - [ ] There are tests for these changes OR - [ ] These changes do not require tests because ___ <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
|
Will the document unload when the window is closed? For example, are we supposed to get an unload event when the glutin window is closed? Also - this indeed fixes #24591 :) |
Yeah I think the problem is not all |
|
@bors-servo try=wpt |
fix unloading, active BC, and clearing js runtime <!-- Please describe your changes on the following line: --> Move the unload steps of the currently active doc to the beginning of the "load" for the new document. Only nullify the window proxy if it's not used by another window. --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: --> - [ ] `./mach build -d` does not report any errors - [ ] `./mach test-tidy` does not report any errors - [ ] These changes fix #24591 (GitHub issue number if applicable) <!-- Either: --> - [ ] There are tests for these changes OR - [ ] These changes do not require tests because ___ <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
|
|
|
Ok so the unloading happens now "earlier", and this breaks something about the history flow. To be investigated. |
|
@bors-servo try=wpt |
fix unloading, active BC, and clearing js runtime <!-- Please describe your changes on the following line: --> Move the unload steps of the currently active doc to the beginning of the "load" for the new document. Only nullify the window proxy if it's not used by another window. --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: --> - [ ] `./mach build -d` does not report any errors - [ ] `./mach test-tidy` does not report any errors - [ ] These changes fix #24591 (GitHub issue number if applicable) <!-- Either: --> - [ ] There are tests for these changes OR - [ ] These changes do not require tests because ___ <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
|
|
|
I think the taskcluster results include intermittents, is there are way to know which ones are "real" failures? |
|
Look at filtered-wpt-errorsummary.log under Artifacts. |
|
thanks, here is
|
|
That crash is one that I would usually associated with #22955. |
Fix unloading, active BC, and clearing js runtime <!-- Please describe your changes on the following line: --> Do not set the window to be the currently active one for the windowproxy as part of `load`, as it will be done later when the document activity is set. And doing it later means that when unload runs, it is with the unloaded pipeline as the active window. Only nullify the window proxy if it's not used by another (currently-active) window. --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: --> - [ ] `./mach build -d` does not report any errors - [ ] `./mach test-tidy` does not report any errors - [ ] These changes fix #24591 (GitHub issue number if applicable) <!-- Either: --> - [ ] There are tests for these changes OR - [ ] These changes do not require tests because ___ <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
|
|
@gterzian Maybe you want to mark this one as |
|
Yep sorry I forgot to push the change with the updated expectation. @bors-servo r=jdm |
|
|
Fix unloading, active BC, and clearing js runtime <!-- Please describe your changes on the following line: --> Do not set the window to be the currently active one for the windowproxy as part of `load`, as it will be done later when the document activity is set. And doing it later means that when unload runs, it is with the unloaded pipeline as the active window. Only nullify the window proxy if it's not used by another (currently-active) window. --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: --> - [ ] `./mach build -d` does not report any errors - [ ] `./mach test-tidy` does not report any errors - [ ] These changes fix #24591 (GitHub issue number if applicable) <!-- Either: --> - [ ] There are tests for these changes OR - [ ] These changes do not require tests because ___ <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
|
|
|
@bors-servo retry |
|
|
Fix unloading, active BC, and clearing js runtime <!-- Please describe your changes on the following line: --> Do not set the window to be the currently active one for the windowproxy as part of `load`, as it will be done later when the document activity is set. And doing it later means that when unload runs, it is with the unloaded pipeline as the active window. Only nullify the window proxy if it's not used by another (currently-active) window. --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: --> - [ ] `./mach build -d` does not report any errors - [ ] `./mach test-tidy` does not report any errors - [ ] These changes fix #24591 (GitHub issue number if applicable) <!-- Either: --> - [ ] There are tests for these changes OR - [ ] These changes do not require tests because ___ <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
|
|
gterzian commentedNov 20, 2019
•
edited
Do not set the window to be the currently active one for the windowproxy as part of
load, as it will be done later when the document activity is set. And doing it later means that when unload runs, it is with the unloaded pipeline as the active window.Only nullify the window proxy if it's not used by another (currently-active) window.
./mach build -ddoes not report any errors./mach test-tidydoes not report any errors