I have seen this with a number of other apps and services, seems whatever is active when the shell crashed grabs all the cpu. One theory is that when a dbus client terminates the service side spins consuming cpu.
I have seen this with a number of other apps and services, seems whatever is active when the shell crashed grabs all the cpu.
One theory is that when a dbus client terminates the service side spins consuming cpu.