[appmgr] Kill realm when its job dies
When realm's job dies, that realm becomes useless because it cannot create any more components aor realms inside of it, so better to kill it and lets realm owner know that realm was killed so that they can exit gracefully or create a new one. This will also complete bug CF-706 because now we have checks in place which ensure that appmgr doesn't crashdue to closed handles when there is a oom. CF-706 #done TEST=fx run-test appmgr_integration_tests Change-Id: I4a06bc73d76fe44a075d63fc3f0f762a94a19a14
Showing
- garnet/bin/appmgr/appmgr.cc 3 additions, 1 deletiongarnet/bin/appmgr/appmgr.cc
- garnet/bin/appmgr/environment_controller_impl.cc 35 additions, 6 deletionsgarnet/bin/appmgr/environment_controller_impl.cc
- garnet/bin/appmgr/environment_controller_impl.h 15 additions, 2 deletionsgarnet/bin/appmgr/environment_controller_impl.h
- garnet/bin/appmgr/integration_tests/realm_integration_test.cc 88 additions, 11 deletions...et/bin/appmgr/integration_tests/realm_integration_test.cc
- garnet/bin/appmgr/job_provider_impl.cc 1 addition, 1 deletiongarnet/bin/appmgr/job_provider_impl.cc
- garnet/bin/appmgr/realm.cc 41 additions, 19 deletionsgarnet/bin/appmgr/realm.cc
- garnet/bin/appmgr/realm.h 11 additions, 5 deletionsgarnet/bin/appmgr/realm.h
Loading
Please register or sign in to comment