几大windows内存出错的应对策略（Several windows memory error coping strategies）.docVIP

几大windows内存出错的应对策略（Several windows memory error coping strategies） Run some larger program or game Windows XP system, the system will automatically pop up often XX memory can not be read or written error, encounter this kind of fault information, how can we be effectively excluded, while ensuring that the next time you run the larger program or game, the system will not appear again system memory read and write wrong? In fact, the use of Windows operating system, people often encounter this error message: The 0memory referenced by the 0X??? directive can not be called read or written, and then the application is closed. If you ask some experts, the answer is often Windows is so unstable and other kind of indignation and disdain. In fact, this error is not necessarily caused by Windows instability. This paper briefly analyzes the general cause of this mistake. First, the application failed to check memory allocation failure The program requires a memory to store data, you need to use the operating system to provide the function to apply, if successful memory allocation, memory area function will be the new return to the application, the application can use this memory via this address. This is called dynamic memory allocation, and the memory address is called the cursor in programming. Memory is not always coming, endless, and sometimes memory allocation will fail. When the allocation fails, the system function returns a 0 value, when the return value 0 does not represent the newly enabled cursor, but a notification sent to the application by the system informing the error. As an application, in the memory after each application should check whether the return value is 0, if it is, it means that there is a fault, some measures should be taken to save, which enhances the robustness of the program. If the application does not check this error, it will follow the thought inertia that the value is allocated to the available cursor, continue to use this memory a