No internet connection
  1. Home
  2. Support

Lately and seemingly at random, SoundFlow will quit. The icon isn't in my menu bar, my Stream Deck is stuck on the SoundFlow icon and I cannot relaunch the app without a reset

By Nathan Salefski @nathansalefski
    2024-02-09 23:17:15.806Z

    Lately, and seemingly at random, SoundFlow will quit. The icon isn't in my menu bar, my stream deck is stuck on the SoundFlow icon and I cannot relaunch the app without a reset. I have no way of replicating it unfortunately.

    System Information

    SoundFlow 5.5.4

    OS: darwin 22.6.0

    ProductName: macOS
    ProductVersion: 13.5.2
    BuildVersion: 22G91

    Steps to Reproduce

    1. N/A

    Expected Result

    N/A

    Actual Result

    N/A

    Workaround

    Other Notes


    Links

    User UID: EoVu20w2ZRTvmJvgozc57ZXuAhU2

    Feedback Key: sffeedback:EoVu20w2ZRTvmJvgozc57ZXuAhU2:-NqF9I8TigR4HT-gibLP

    Feedback ZIP: n31V4QUn5A+jLMcXGoLku7zXCj3u9yDufYxSiyBsEKMFZPoJ+VB2U5C9rxCiiz+B61/f0ppnFn1O34bILedQYX4txJCISeqJPN4CSIF2n/51Ggsd13XKOjHxUkCd+h9BNVS/MWgwI3AyriM9g2iBulIbW5XhG3tmk/13wdZbRWzRcbtvVHe9ivCpsk0UN+dmPZH9+uojSXdatFsYFI/hQux8WFLv8+HM/GvValDzDkTZ7SjkZSBEhZbIyb8HOZnA27KH0gETK5quPqFk/zpt8BKFgXVhYqW4TZDWENw8C+JbqKrld4MGkJJ4WeFaW9/2twcxuyM1UYRg3m54MUYjfcQHOWrlv++GhUI/lxL2Q6s=

    • 15 replies
    1. Nathan Salefski @nathansalefski
        2024-02-09 23:19:06.654Z

        Below is a Screen Recording and a Picture of my Stream Deck. I hope that helps in some way.

        https://www.dropbox.com/scl/fi/umbxnp8hsvvilrkezt1fi/SoundFlow-Frozen.mov?rlkey=nipqvyiin9ixnzyi9srwxya6e&dl=0

        1. Kitch Membery @Kitch2024-02-09 23:25:23.592Z

          Hi Nathan,

          Thanks for reporting this.

          As a troubleshooting step can you try reinstalling the latest version of SoundFlow from my.soundflow.org/install

          Let me know if after doing so, the issue persists. Thanks in advance.

          1. Nathan Salefski @nathansalefski
              2024-02-09 23:32:44.975Z

              Reinstalling now. I'll keep you posted.

              1. In reply toKitch:
                Nathan Salefski @nathansalefski
                  2024-02-10 20:57:29.528Z

                  Just happened again. I'll wait to reset my computer incase you have some steps you'd like me to follow

                  1. Kitch Membery @Kitch2024-02-10 21:02:23.090Z

                    Thanks for letting me know. If you could reopen SoundFlow and log another bug report that would be great, just to make sure we have the log files. Be sure to note the time at which it happen so we can investigate.

                    1. Nathan Salefski @nathansalefski
                        2024-02-10 21:03:21.001Z

                        I can't reopen SoundFlow without restarting. Restarting won't cause any issue with the logs will it?

                        1. Kitch Membery @Kitch2024-02-10 21:04:37.458Z

                          That’s fine. The logs are kept for 5days I believe. :-)

                          1. Nathan Salefski @nathansalefski
                              2024-02-10 21:09:17.365Z
                              1. Hi Nathan,

                                I can see in your log files that SF's backend process is indeed crashing. I can also see some attempts at starting up SoundFlow again that are failing because one of the processes are still running in the background.
                                It looks like you then restarted your computer which made things work again. Another time, you should be able to run this code in Terminal to kill all processes related to SoundFlow:

                                pkill -9 SoundFlow
                                
                                1. Nathan Salefski @nathansalefski
                                    2024-02-10 23:14:27.562Z

                                    Awesome thanks Christian. Any idea what’s causing that? So I can avoid it if possible

                                    1. I couldn't see in the logs why the crash happened in the first place, unfortunately. It looks like it "only" happened one time yesterday (everything else was failed attempts at launching because the sfbackend process was still running), so I bet it must be difficult to troubleshoot if it doesn't happen more often.

                                      One guess could be hardware that's attached - but I'm really not sure.

                                      1. Nathan Salefski @nathansalefski
                                          2024-02-10 23:49:51.787Z

                                          All good. For now I’ll keep that terminal command handy

                                      2. In reply tochrscheuer:
                                        Nathan Salefski @nathansalefski
                                          2024-02-11 00:12:23.900Z

                                          It just stopped working once again and I tried this without any luck

                                          1. Can I get you to send us a new report? Please note in it:
                                            a) the time it crashed - how does that look?
                                            b) the time you ran the Terminal code to clean out any processes
                                            c) the time you attempted to launch SF again afterwards

                                            We can use this information to compare against the log's timestamps to better know which errors correlate to which action you're taking.