[timidity-talk] Spinning

[Aaron W. <wal...@gm...>]

Hello, guys and gals,
Already posted a question here, so cross post:
https://askubuntu.com/questions/1298529/timidity-occasionally-running-amok

Here's the essential body of the question:
******

Running Ubuntu Studio 20.04. Occasionally I'll look out there and find
timidity running, using up a whole CPU. I have not found the reason for
this... it does not appear to be in use by any of the apps I am running
(and can shut them all down, with timidity still spinning).

I'm looking at the syslog, and I can see:

syslog.1:Dec  8 07:14:31 Parker systemd[1]: Starting LSB: start and
stop timidity...
syslog.1:Dec  8 07:14:32 Parker timidity[713]:  * Starting TiMidity++
ALSA midi emulation timidity
syslog.1:Dec  8 07:14:32 Parker timidity[713]:    ...done.
syslog.1:Dec  8 07:14:32 Parker systemd[1]: Started LSB: start and
stop timidity.

That appears to be at boot. I have not had success in reproducing this.
Most times, I boot up, and check, and it's not running. Sometimes, it's
spinning. So, perhaps sometimes the "stop timidity" doesn't happen. Any
suggestions on how to track this down?

It's working hard!

me@Parker:/var/log$ who -b
         system boot  2020-12-08 07:14
me@Parker:/var/log$ date
Tue 08 Dec 2020 10:58:03 AM EST
me@Parker:/var/log$ ps -o lstart= -p 847
Tue Dec  8 07:14:31 2020
me@Parker:/var/log$ ps -o %cpu,%mem,cmd -p 847
%CPU %MEM CMD
94.7  0.0 /usr/bin/timidity -Os -iAD
******

Additionally, I've been experimenting, trying to figure out a trigger, but
have had little luck yet.
I run with Jack, which I control with Jack audio connection kit.  In
addition, I have the following script run after startup:
/usr/bin/a2jmidid -e &

So, at this moment, I have timidity running at 100%.  Jack is running.
I stop Jack (through the connection kit), and I see that timidity process
stays out there, but stops spinning.
I start Jack again, and timidity goes back up to 100%.
I stop Jack again, goes back down.  Then when I start it again, timidity
does not shoot back up.  Very odd.
Not suggesting that this "2nd time it stops" is normal or indicative.  Just
reporting what happened in this case.
Any suggestions?

Thanks!