A page fault in operating system happens when a program endeavors to get to a square of memory that isn't put away in the physical memory or RAM. The issue advises the working framework that it must find the information in virtual memory, at that point move it from the capacity gadget, for example, an HDD or SSD, to the framework RAM.
In spite of the fact that the expression "page fault" seems like a blunder, page issues are normal and are a piece of the ordinary way PCs handle virtual memory. In programming terms, a page deficiency produces an exemption, which informs the working framework that it must recover the memory squares or "pages" from virtual memory all together for the program to proceed. When the information is moved into physical memory, the program proceeds as ordinary. This procedure happens out of sight and ordinarily goes unnoticed by the client.
Most page faults are taken care of with no issues. Be that as it may, an invalid page flaw may make a program hang or crash. This kind of page deficiency may happen when a program attempts to get to a memory address that doesn't exist. A few projects can deal with these kinds of blunders by finding another memory address or moving the information. Be that as it may, if the program can't deal with the invalid page flaw, it will get went to the working framework, which may end the procedure. This can make the program suddenly quit.
While page fault is regular when working with virtual memory, each page shortcoming requires moving information from optional memory to essential memory. This procedure may just take a couple of milliseconds, yet that can in any case be a few thousand times more slowly than getting to information straightforwardly from memory. Consequently, introducing more framework memory can expand your PC's presentation, since it should get to virtual memory less regularly.
Comments