Script: ensure child JS runtimes are dropped before parent#30896
Script: ensure child JS runtimes are dropped before parent#30896mrobinson merged 5 commits intoservo:mainfrom
Conversation
|
Looks like this is just failing due to a tidy issue. It should be fixed with |
|
See #30124 (comment) for an exaplanation, and I think the conclusion is that every time script crashes, we drop the "top" runtime as part of See servo/components/script/script_thread.rs Line 755 in 205d52a Compare with the "clean" version which is followed on orderly shutdown of a pipepline: servo/components/script/script_thread.rs Line 2984 in 205d52a |
|
Upon further investigation, this doesn't seem to fix the problem, so I'll investigate further... |
|
Ok so this required different fixes, because each linked-to issues was actually hitting a different problem. All are covered now. @mrobinson r? |
jdm
left a comment
There was a problem hiding this comment.
This makes sense! My only question is whether we should use an object with a Drop impl that could replace the manual calls in the dedicated worker code?
|
|
I'm not concerned about safety, just avoiding any other early return branches where the same fix should be applied but might be missed. |
It appears to not work for now, Have also added a manual branch to the |
|
note to self: use |
|
🔨 Triggering try run (#7393899054) with platforms=linux,macos,windows and layout=undefined |
|
Test results for linux-wpt-layout-2013 from try job (#7393899054): Flaky unexpected result (16)
Stable unexpected results that are known to be intermittent (17)
|
|
Test results for linux-wpt-layout-2020 from try job (#7393899054): Flaky unexpected result (12)
Stable unexpected results that are known to be intermittent (15)
|
|
✨ Try run (#7393899054) succeeded. |
|
I'll send this to the merge queue since I think all issues are resolved now. |
Remove the annoying
This runtime still has live children.that keeps showing up.Many issues that contain that backtrace as opposed to the actual underlying problem:
FIX #30124
FIX #24168
FIX #25729
FIX #28357
FIX #26778
Marking them as fixed, because it appears to me that the original panic is already filed in other issues(i've pointed it out in each issue).
./mach build -ddoes not report any errors./mach test-tidydoes not report any errors