Skip to content

jfilter stuck at 100% CPU after xrun #2

@kylerbrown

Description

@kylerbrown

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.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions