[bug] App stutters and crashes when loading existing presets #68

Activity

1. wjc100200

   added

   bugSomething isn't workingSomething isn't working

   on Oct 24, 2026
2. Horuse commented on Oct 25, 2026

   

   Horuse

   on Oct 25, 2026

   Owner

   More actions

   Thanks for the report. First, just to make sure we're talking about the same thing: by "preset" do you mean an effect preset (the one you pick inside a node like EQ or Compressor), or a whole pipeline from the main screen?

   Either way, please tell me what's in it, since this may only happen with certain effects. Which effects or nodes does it use? Any plugins (VST3/CLAP)? Which audio devices: Bluetooth, USB or virtual cables? Does it use App Audio capture? A screenshot of the graph helps a lot.

   When you start Splitwave again after the crash, does it show a crash report window? If it does, click the copy button and paste what it gives you here. Also, what does the crash look like: does the window just close, turn white, or hang with "Not responding"?
3. wjc100200 commented on Oct 25, 2026

   

   wjc100200

   on Oct 25, 2026 via email

   Author

   More actions

   It’s the whole pipeline from the main screen — I built this pipeline myself, and it is not a preset. I’m not using any VST3/CLAP plugins; it only uses Splitwave’s built-in nodes. The devices used are USB-connected headphones and a VB-Audio virtual cable. I’m not using App Audio capture. The input uses only Microphone, and the output uses only Speaker. When it crashes, it hangs and shows “Not responding”. ## Diagnostic info - **App:** Splitwave 1.4.1 (tauri 2.11.1) - **OS:** windows 10.0.26100 (x86_64) - **Source:** unexpectedExit (thread: <unknown&gt;) - **Time:** 2026-10-25T12:54:53.294Z **Message:** ``` Splitwave did not shut down cleanly ``` **Stack:** ``` No native stack was captured. The process may have been killed by the OS, an out-of-memory condition, or a native crash without a dump. ``` <!-- Screenshots, logs, related issues, anything else useful. --&gt;

   …

   ------------------&nbsp;原始邮件&nbsp;------------------ 发件人: "Horuse/Splitwave" ***@***.***&gt;; 发送时间:&nbsp;2026年10月25日(星期天) 晚上8:51 ***@***.***&gt;; ***@***.******@***.***&gt;; 主题:&nbsp;Re: [Horuse/Splitwave] [bug] App stutters and crashes when loading existing presets (Issue #68) Horuse left a comment (Horuse/Splitwave#68) Thanks for the report. First, just to make sure we're talking about the same thing: by "preset" do you mean an effect preset (the one you pick inside a node like EQ or Compressor), or a whole pipeline from the main screen? Either way, please tell me what's in it, since this may only happen with certain effects. Which effects or nodes does it use? Any plugins (VST3/CLAP)? Which audio devices: Bluetooth, USB or virtual cables? Does it use App Audio capture? A screenshot of the graph helps a lot. When you start Splitwave again after the crash, does it show a crash report window? If it does, click the copy button and paste what it gives you here. Also, what does the crash look like: does the window just close, turn white, or hang with "Not responding"? — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***&gt;