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 upIntermittent Result::unwrap() panic in WPT reftest ("Connection reset by peer" or "Couldn't receive FontCacheThread") #8815
Labels
Comments
This was referenced Jan 15, 2016
|
These might be caused by servo/ipc-channel#29. |
This was referenced Jan 20, 2016
|
This will hopefully be solved by servo/ipc-channel#30. |
frewsxcv
added a commit
that referenced
this issue
Jan 28, 2016
servo/ipc-channel@dfd8513...4cc8773 Attempt to fix #8815
bors-servo
added a commit
that referenced
this issue
Jan 28, 2016
Upgrade ipc-channel dependency. servo/ipc-channel@dfd8513...4cc8773 Attempt to fix #8815 <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.svg" height="40" alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/9445) <!-- Reviewable:end -->
|
Still happening. |
|
|
Unfortunately the stack here is much less informative than the original ones that prompted servo/ipc-channel#29 :( |
This was referenced Jan 30, 2016
This was referenced Mar 24, 2016
Merged
This was referenced Apr 22, 2016
emilio
added a commit
to emilio/servo
that referenced
this issue
May 12, 2016
One of these two unwraps is the one that is causing servo#8815. I'd go with removing the second unwrap entirely, but let's get some debug info first, since it might probably be a race.
emilio
added a commit
to emilio/servo
that referenced
this issue
May 12, 2016
One of these two unwraps is the one that is causing most occurrences of servo#8815. I'd go with removing the second unwrap entirely, but let's get some debug info first, since it might probably be a race.
emilio
added a commit
to emilio/servo
that referenced
this issue
May 12, 2016
One of these two unwraps is the one that is causing most occurrences of servo#8815. I'd go with removing the second unwrap entirely, but let's get some debug info first, since it might probably be a race.
bors-servo
added a commit
that referenced
this issue
May 12, 2016
gfx: Add expect messages to FontCacheThread::exit() Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [ ] These changes fix #__ (github issue number if applicable). Either: - [ ] There are tests for these changes OR - [x] These changes do not require tests because they only add debug info. Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. One of these two unwraps is the one that is causing most occurrences of #8815. I'd go with removing the second unwrap entirely, but let's get some debug info first, since it might probably be a race.
|
Since most of the occurrences of this now happen in It's probably a race, but if it's not really important (something like the other side has already exited) and we don't care a lot (that depends on what the other side is and expects), we could drop the |
bors-servo
added a commit
that referenced
this issue
May 12, 2016
gfx: Add expect messages to FontCacheThread::exit() Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [ ] These changes fix #__ (github issue number if applicable). Either: - [ ] There are tests for these changes OR - [x] These changes do not require tests because they only add debug info. Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. One of these two unwraps is the one that is causing most occurrences of #8815. I'd go with removing the second unwrap entirely, but let's get some debug info first, since it might probably be a race. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/11166) <!-- Reviewable:end -->
|
zakorgy
added a commit
to zakorgy/servo
that referenced
this issue
May 26, 2016
One of these two unwraps is the one that is causing most occurrences of servo#8815. I'd go with removing the second unwrap entirely, but let's get some debug info first, since it might probably be a race.
|
Seems to have disappeared. |
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-comments-removed
that referenced
this issue
Oct 1, 2019
…ipc-channel); r=jdm servo/ipc-channel@dfd8513...4cc8773 Attempt to fix servo/servo#8815 Source-Repo: https://github.com/servo/servo Source-Revision: 0cd034041f5859d6bc6f302f03376ae276611ebf UltraBlame original commit: 5fd5b0576e5cf40fae1df5f3acd1a4519ff879e1
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-wordified-and-comments-removed
that referenced
this issue
Oct 1, 2019
…ipc-channel); r=jdm servo/ipc-channel@dfd8513...4cc8773 Attempt to fix servo/servo#8815 Source-Repo: https://github.com/servo/servo Source-Revision: 0cd034041f5859d6bc6f302f03376ae276611ebf UltraBlame original commit: 5fd5b0576e5cf40fae1df5f3acd1a4519ff879e1
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-wordified
that referenced
this issue
Oct 1, 2019
…ipc-channel); r=jdm servo/ipc-channel@dfd8513...4cc8773 Attempt to fix servo/servo#8815 Source-Repo: https://github.com/servo/servo Source-Revision: 0cd034041f5859d6bc6f302f03376ae276611ebf UltraBlame original commit: 5fd5b0576e5cf40fae1df5f3acd1a4519ff879e1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This looks like a case of the layout/script threads already having shut down and the constellation racing to communicate with them.