by fddima » Sun Jan 22, 2017 4:58 am
There is exist not so many reasons to remain ghost renderer or gpu process: chromium code also not ideal and has lot of TODOs (thanks to mojo). But in most cases if you will wait long enough - they should be closed anyway.
If you not happy with chromiums process monitoring/shutdown - you always can implement own by utilizing parent/child process relationship. I'm somewhere on this forum describe this more precisely. But this kind of additional protection really needed usually very rarely / kind of workaround / soft fixing chrome code without touching chrome code.
You should understand - chrome has same defects, but usually we so rare close browser that we never hit. When you develop app - run cycles 10-100x times more, process aborts, so nightmare cases occurs which never normally occurs in release/chrome.