© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
OK, it looks like it's cpp that's taking up the memory. Although it's interesting it froze at only 10 GB. Perhaps the last uptick of memory consumption happened fast enough to not make it to the system monitor.
So, this is an interesting bug in gcc, I guess?
I wonder if others can confirm the following for their hard freezes:
1) is it because the RAM is totally consumed?
2) if so, what process is consuming the RAM?
In any case, I wonder why running out of RAM causes a hard freeze: isn't that what swap files are for? I.e. gcc may be misbehaving, but isn't the system also not responding very well to gcc's misbehaviour? On a system level, shouldn't it swap out? On a user experience level, regardless of the lack of swapping, couldn't the process be halted, since the whole system is about to be unusable anyway?