After an xrun, the jfilter ports are closed on the JACK server, but the process continues, consuming 100% CPU until it is killed by hand. Ideally, an xrun shouldn't kill jfilter, as this only happens on start-up sometimes.