-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
reviver/replacer is slow #36972
Comments
jrieken
added a commit
that referenced
this issue
Dec 4, 2017
alexdima
added a commit
that referenced
this issue
Dec 13, 2017
alexdima
added a commit
that referenced
this issue
Dec 13, 2017
alexdima
added a commit
that referenced
this issue
Dec 13, 2017
alexdima
added a commit
that referenced
this issue
Dec 13, 2017
alexdima
added a commit
that referenced
this issue
Dec 13, 2017
alexdima
added a commit
that referenced
this issue
Dec 13, 2017
alexdima
added a commit
that referenced
this issue
Dec 13, 2017
alexdima
added a commit
that referenced
this issue
Dec 13, 2017
alexdima
added a commit
that referenced
this issue
Dec 13, 2017
This can be configured per proxy now. Let's track the adoption in #40169 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have a reviver and replacer function for the extension host communication that ensure regular expressions and URIs are always what you would expect. This is convenient but also slow because the reviver visits every object. We should manually convert those (as we do with any other type as well)
The text was updated successfully, but these errors were encountered: