Comment 2 for bug 1878723
Revision history for this message
| Eric Detheridge (ericdetheridge) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
I also experienced this bug today. What seems to have happened is that upstart init filled all of the memory on my machine while libjson-c2 was updating, leading to oom-killer killing everything. The kernel panic here would happen if oom-killer tries to act on init. After a reboot my machine managed to upgrade fully before crashing due to running out of memory again.