This is how/why the same buggy/crashing/broken software on XP will run smoothly on Windows 7/8/10. If anyone has ever wondered how ALL software on Windows 7 started to be more 'stable' - it is because of these technologies that fix 3rd party software and even drivers. XP introduced a very basic version of this, but Vista and then 7/8 expanded these technologies with new real-time monitoring at more levels, virtualization tricks, and the compatibility database that preemptively fixes errors in software. There is a chance that even this issue with Chrome will slowly crash less often on your system if Windows is able to keep identifying the bugs and fixing them as they happen. This is also why it is recommended that if you find a piece of software that fails to launches or crashes, that you keep running it a few times, to let Windows 'learn' the bugs and try to fix/compensate for them. This is why software that 'once' ran glitchy or crashed, will start to run without issues - as Windows learns to correct the software and then adds that information to the compatibly database. The first catches API bugs and memory allocation issues and other things in the Windows subsystem - the lower one (added in 8 I think) will catch and correct things like kernel drivers and is even capable of noticing and fixing a CPU instruction in real-time.Īs the real-time system detects problems and attempts to fix them, the issues are added to the compatibility database and when running the software in the future, the first set of bugs/issues will be compensated for and additional 'new' bugs detected by the real-time system will keep attempting to fix them to keep the software running and stable. This real-time compatibility systems that will attempt to fix issues on unknown software bugs - one that runs at a higher application level and one that runs in the kernel. One lesser known features of Windows is that it has an entire compatibility database and real-time systems it uses to 'fix' known 3rd party software errors - from adjusting API bugs all the way down to fixing CPU specific instructions. (Which I'm glad they do, as end users are more important that who did what - even though they often will take the perception of fault when it wasn't them.) I am curious, as I know that Microsoft will often take a hit just to help users and get software running well and issue a compatibility database update or if this is something they will fix in Windows itself. Was the problem in the franken-stack Chromium uses for GPU access on Windows, drivers updates, or a change in Windows itself?
0 kommentar(er)
