New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hold stderr lock when using stdout through Console APIs. #17360
Merged
+65
−37
Merged
Changes from all commits
Commits
File filter...
Filter file types
Jump to…
Jump to file
Failed to load files.
ProTip!
Use n and p to navigate between commits in a pull request.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Also, I wonder whether we should split this loop (and the others) into two, one that does the printing with the lock held, and other that calls
send_to_devtools.I say that, because as far as I can tell, that function can panic and log (it uses
downcast, which callsget_dom_class, which doestrace!, which writes to stderr I think). I'd expect this to deadlock withRUST_LOG=trace, wouldn't it? or is the lock re-entrant? If it is, please comment on it.