(In reply to James Forshaw from comment #6) ... > I'll let you know when I having something in the Chromium repo to test. Of course if you have other ideas it'd be good to know. Thanks James, no other ideas at the moment, but I'm continuing to try and track down the other performance regressions. Sounds like that will definitely render my OpenProcessToken fix unnecessary, hopefully it will sort the other performance regressions as well. We were already planning to break the DirectCache deliberately at some point assuming that we would hit the same reconnection issue that you had, but we'll probably only do that when we have the accelerated rendering moved to the GPU process.
Bug 1618911 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to James Forshaw from comment #6) ... > I'll let you know when I having something in the Chromium repo to test. Of course if you have other ideas it'd be good to know. Thanks James, no other ideas at the moment, but I'm continuing to try and track down the other performance regressions. Sounds like that will definitely render my OpenProcessToken fix unnecessary, hopefully it will sort the other performance regressions as well. We were already planning to break the DirectWrite cache deliberately at some point assuming that we would hit the same reconnection issue that you had, but we'll probably only do that when we have the accelerated rendering moved to the GPU process.