Soundflow unresponsive several time a day on multiple devices
System Information
SoundFlow 5.3.2
OS: darwin 21.6.0
ProductName: macOS
ProductVersion: 12.6.5
BuildVersion: 21G531
Steps to Reproduce
Expected Result
Actual Result
Workaround
Other Notes
The last fews weeks, both my Stream Deck and Android tablet have been been getting quite buggy several times a day. It had been rock solid until then. Any of the following will happen...
-the buttons become unresponsive
-there's a lag of 5-10 seconds after pressing a button before a command executes
-the Stream Deck reverts to the Sound Flow logo
-the tablet will go to a blank screen, other than the Sound Flow logo in the corner
-the tablet will revert to the list of Decks available
-the tablet will revert to the list of computers available
Functionality seems to come back after a few minutes, but everything will be unresponsive in the meantime.
v5.3.2 is installed on OS 12.6.5
Links
User UID: bFjAgiBx9vf9EF9QDxr5s2xSx3E3
Feedback Key: sffeedback:bFjAgiBx9vf9EF9QDxr5s2xSx3E3:-NVVXX74HzqSioMPXv20
Christian Scheuer @chrscheuer2023-05-15 18:53:38.490ZHi Ian,
Thanks for reporting this. I see the following in your log file:
15.05.2023 13:29:27.77 <info> [Backend]: PopupMenu full role:AXMenu 15.05.2023 13:29:27.78 <info> [Backend]: NOT YET IN AX MODE 15.05.2023 13:29:27.78 <info> [Backend]: Clicking popup menu with PT2022.5+ implementation 15.05.2023 13:29:27.78 <info> [Backend]: Clicking popup menu element: Batch Rename... 15.05.2023 13:29:34.96 <error> [BackendConnection]: Keep Alive error: Request timeout Request timeout 15.05.2023 13:29:34.96 <info> [BackendConnection]: Ping results = true, true, false 15.05.2023 13:29:44.97 <error> [BackendConnection]: Keep Alive error: Request timeout Request timeout 15.05.2023 13:29:44.97 <info> [BackendConnection]: Ping results = true, false, false 15.05.2023 13:29:54.98 <error> [BackendConnection]: Keep Alive error: Request timeout Request timeout 15.05.2023 13:29:54.99 <info> [BackendConnection]: Ping results = false, false, false 15.05.2023 13:29:54.99 <info> [BackendConnection]: Backend didn't respond to our pings, so recycle it: Request timeout 15.05.2023 13:29:56.60 <info> [BackendConnection]: Backend quit unexpectedly with exitCode: nullThis indeed indicates that something makes SoundFlow unresponsive (it then restarts itself because it detects it, but that takes a little while)
Christian Scheuer @chrscheuer2023-05-15 18:55:50.667ZThe next time it happens where it feels stuck, it would be helpful if you can open up Activity Monitor and see if anything is going on. It could be that the SoundFlow process is using 99% of the CPU or something.
If that happens, it's helpful if you can get a "Sample" of the process. This means clicking the "Info" ("I") button to open up info about the process, then clicking the "Sample" button. This tells us more about why it's using too much CPU / where it's stuck
Ian Bodzasi @Ian_BodzasiThanks Christian! Not sure if this is related, but today I've been finding typing text while in various programs intermittently very laggy....5-10+ seconds behind at times. Noticed that Sound Flow was using 100% of CPU, so I grabbed a log file from Activity Monitor.
When pasting the text from the log file here, I get the following error, is there a better way to send it?
Error 413 Payload Too Large
For request 'POST /-/reply' [Request Entity Too Large]See server logs for stack trace. [EdEGOTHTML]
Much thanks!
- Christian Scheuer @chrscheuer2023-05-23 17:19:34.829Z
Thanks! You can ZIP the file and upload it to dropbox/google drive and share a link here, that's probably the easiest.
- Ian Bodzasi @Ian_Bodzasi
Great, thanks. Here's a link...
- In reply tochrscheuer⬆:Ian Bodzasi @Ian_Bodzasi
Hey Christian, here's another sample where Soundflow was taking 100% of the CPU a few minutes before it crashed & restarted. Thanks!
- In reply tochrscheuer⬆:Ian Bodzasi @Ian_Bodzasi
Hi @chrscheuer, just wanted to follow up on this. I've added an ethernet adaptor to the tablet rather than relying on the wifi, and it's been rock solid since. I saw you mention on another thread that certain routers can act weird between the wired & wireless networks, it looks like that was likely the case here!
- Christian Scheuer @chrscheuer2023-07-12 19:22:25.331Z
Awesome, thank you so much for sharing!
- SIn reply toIan_Bodzasi⬆:SoundFlow Bot @soundflowbot
This report was now added to the internal issue tracked by SoundFlow as SF-751
- SIn reply toIan_Bodzasi⬆:SoundFlow Bot @soundflowbot
The linked internal issue SF-751 has been marked as Done