Changes between Initial Version and Version 1 of Ticket #9011, comment 23
- Timestamp:
- May 12, 2012 4:14:56 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #9011, comment 23
initial v1 1 Clearly what seems to be happening is that some process ends up using up a lot of RAM, perhaps fi fefox, the system runs out of RAM as a result. Normally Linux will kill the most memory hungry application so that other programs who need memory can have some. Apparently this is not happening very quickly. Instead, the system now grinds to a near halt and it may be an hour before Firefox is finally killed by the kernel.1 Clearly what seems to be happening is that some process ends up using up a lot of RAM, perhaps firefox, the system runs out of RAM as a result. Normally Linux will kill the most memory hungry application so that other programs who need memory can have some. Apparently this is not happening very quickly. Instead, the system now grinds to a near halt and it may be an hour before Firefox is finally killed by the kernel. 2 2 3 3 Then the system unfreezes and returns to normal. 4 4 5 I have seen many times the error messages announcing that oomkiller is killing the firefox process. Then the system on freezes.5 I have seen many times the error messages announcing that oomkiller is killing the firefox process. Then the system un freezes. 6 6 7 7 Recently as well, I have been recieving error messages such as , i am paraphrasing: "Cannot fork, cannot allocate memory" during the freezeup period before Linux kills a process to free more RAM.
