5 ms·
tl;dr the method presence pulls in a dependency that runs slow buggy code. so click bait.
by gcb0 8y ago
tl;dr the method presence pulls in a dependency that runs slow buggy code.
so click bait.
- saagarjha 8y agoI don't think that's quite right: the method presence pulls in a dependency, but the code is not buggy and the slow bit is the loading of the dependency itself.
- masklinn 8y agoTechnically it's not even the loading of the dependency but its unloading: cleaning up GDI objects[0] on process destruction has become much slower in W10AE and a system-global lock is held during that event. [0] some of which are created automatically when a specific dll is loaded, possibly transitively
- vanderZwan 8y agoThat sounds like there might be other programs with severe regressions out there
- pjc50 8y agoThis is a stupid dismissal of a well-written piece of investigative debugging. This article is the kind of thing I'd like to see more of on HN.
- jackewiehose 8y agoI also liked the article but to be fair, the title is actually a little clickbaity. The slowdown has nothing to do with not-called functions, it's just about DLL-dependencies.
- mark-r 8y agoNot clickbaity at all, it's the essence of what makes the problem interesting. The fact that a DLL dependency can slow down your program at shutdown is not at all intuitive, particularly when it's a system DLL that should be bullet-proof.
- wtracy 8y agoThat doesn't begin to describe the problem: The presence of an unused dependency causes the entire operating system to briefly stop processing input events. A background process could have this problem and you would see performance apparently drop through the floor for completely unrelated processes. I honestly would have been tempted to give this article the clickbait title: "Windows has a DoS vulnerability in the GDI subsystem".