/2 I assume the problem at this date is NOT very well known. But If you look for threads about this problem you can at least go back for more than a year! So if that already got microsofts attention in general and not only for chrome, that would be nice to know. Thank you!
Ah-ha, agreed. I have no useful performance stats, but it does bring a tear to my eye seeing how expensive indirect branches are for so little benefit 
-
-
The cost of each indirect branch is about as small as you could want, even relative to seeing little benefit: page faults aside, there's just a quick diversion to NTDLL to test a bitmap. The big cost is in the preparation and maintenance - and not entirely as designed trade-offs.
-
We have in addition, very plausibly, some inadequately anticipated side-effects and, certainly, at least one silly coding error. If you're correct that CFG does no good at any cost, let alone at a high surprise cost, then why does anyone recommend it not be disabled? Kill it off?
- 4 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
