Is tauri::ipc::Response slower after build？

[Horbin-Magician]

I noticed that tauri::ipc::Response is slower after build, is this a bug?

System: MacOS 15.5, CPU: M4
Tauri version: 2.6.2

Code:

#[tauri::command]
pub async fn capture_screen(webview_window: tauri::WebviewWindow) -> tauri::ipc::Response {
    let masks_arc = {
        let mut app = Application::global().lock().unwrap();
        app.get_module("screenshot")
            .and_then(|s| s.as_any().downcast_ref::<ScreenShotter>())
            .map(|screenshot| screenshot.masks.clone())
    };
    
    let image = if let Some(masks_arc) = masks_arc {
        let masks = masks_arc.lock().await;
        masks.get(webview_window.label()).cloned()
    } else { None };
    tauri::ipc::Response::new(image.unwrap_or_default())
}

When use tauri dev --release, it costs about 10 ms; and when use tauri dev build, it costs about 500 ms. (It's just judged by feeling)

I just replaced tauri::ipc::Response::new(image.unwrap_or_default()) with tauri::ipc::Response::new(vec::new()) and everything returned to normal.

[FabianLars]

hmm i don't see why that would be the case. The IPC should work the same 🤔 Not impossible of course since the security checks may be a bit different but i don't see how that could end up in such a difference.

[Horbin-Magician]

hmm i don't see why that would be the case. The IPC should work the same 🤔 Not impossible of course since the security checks may be a bit different but i don't see how that could end up in such a difference.

Thank you for your reply!
I am also quite confused. And this seems rather difficult to debug.

[Horbin-Magician]

hmm i don't see why that would be the case. The IPC should work the same 🤔 Not impossible of course since the security checks may be a bit different but i don't see how that could end up in such a difference.

I used build --release and found a key error message in dev-tools:

[Error] Refused to connect to ipc://localhost/plugin%3Awindow%7Cis_visible because it appears in neither the connect-src directive nor the default-src directive of the Content Security Policy.
[Warning] IPC custom protocol failed, Tauri will now use the postMessage interface instead – TypeError: Load failed (user-script:3, line 102)

My problem can be solved by adding below content to tauri.conf.json:

  "app": {
    "security": {
      "csp": "default-src 'self' 'unsafe-inline'; connect-src 'self' ipc://localhost",
    }
  }

I don't know whether this is a feature or a bug.

[Think-M]

Can you give WebSocket a try? It might be much faster than invoke!
I now believe that there must be some performance issues with the invoke communication, and it may even be inferior to WebSocket.

[Horbin-Magician]

Can you give WebSocket a try? It might be much faster than invoke! I now believe that there must be some performance issues with the invoke communication, and it may even be inferior to WebSocket.

Are you referring to https://tauri.app/plugin/websocket/? I'll give it a try.
Thank you for your reply!

[Think-M]

Can you give WebSocket a try? It might be much faster than invoke! I now believe that there must be some performance issues with the invoke communication, and it may even be inferior to WebSocket.您可以试试 WebSocket 吗？它可能比调用快得多！我现在认为，调用通信肯定存在一些性能问题，甚至可能不如 WebSocket。

Are you referring to https://tauri.app/plugin/websocket/? I'll give it a try. Thank you for your reply!感谢您的回复！您是指 https://tauri.app/plugin/websocket/ 这个吗？我试试看。

What I mean is to create a WebSocket server in Rust and a client in JavaScript, and then establish communication between them. You can choose to use a WebSocket plugin, but I suggest writing the WebSocket part yourself, as WebSocket plugins may not necessarily be free from performance issues

[Horbin-Magician]

Can you give WebSocket a try? It might be much faster than invoke! I now believe that there must be some performance issues with the invoke communication, and it may even be inferior to WebSocket.您可以试试 WebSocket 吗？它可能比调用快得多！我现在认为，调用通信肯定存在一些性能问题，甚至可能不如 WebSocket。

Are you referring to https://tauri.app/plugin/websocket/? I'll give it a try. Thank you for your reply!感谢您的回复！您是指 https://tauri.app/plugin/websocket/ 这个吗？我试试看。

What I mean is to create a WebSocket server in Rust and a client in JavaScript, and then establish communication between them. You can choose to use a WebSocket plugin, but I suggest writing the WebSocket part yourself, as WebSocket plugins may not necessarily be free from performance issues

I get it, and have a try! But WebSocket cost more time than IPC (If don't consider the abnormal performance problem after build).
WebSocket takes 50 ms to transfer a 20 mb picture, and IPC only takes about 10 ms (all in debug mode).

BTW: I already know why IPC will have performance problems after build, if you are interested, please refer to my latest reply.

[Think-M]

Can you give WebSocket a try? It might be much faster than invoke! I now believe that there must be some performance issues with the invoke communication, and it may even be inferior to WebSocket.

Are you referring to https://tauri.app/plugin/websocket/? I'll give it a try. Thank you for your reply!

What I mean is to create a WebSocket server in Rust and a client in JavaScript, and then establish communication between them. You can choose to use a WebSocket plugin, but I suggest writing the WebSocket part yourself, as WebSocket plugins may not necessarily be free from performance issues

I get it, and have a try! But WebSocket cost more time than IPC (If don't consider the abnormal performance problem after build). WebSocket takes 50 ms to transfer a 20 mb picture, and IPC only takes about 10 ms (all in debug mode).

BTW: I already know why IPC will have performance problems after build, if you are interested, please refer to my latest reply.

Are you using 127.0.0.1 or localhost? 127.0.0.1 may be tens of milliseconds faster than localhost

[Horbin-Magician]

I used localhost, thanks for your reminder!