BUG: Tauri frontend exits after startup with Error 1412 (Chrome_WidgetWin_0)

### Is there an existing issue for this?

- [x] I have searched the existing issues

### What happened?

Description

While running PictoPy locally on Windows 11, the Tauri frontend starts successfully but exits shortly after showing “Waiting for servers to start”.
The backend and sync microservice continue to run correctly, but the desktop app window closes.

The terminal consistently logs the following error:

ERROR: Failed to unregister class Chrome_WidgetWin_0. Error = 1412

This appears to be a Windows 11–specific WebView / Tauri issue, not a frontend or backend crash.

Environment

OS: Windows 11

Node.js: (installed, used by Vite)

Frontend: Vite + Tauri

Backend: FastAPI (Uvicorn)

Sync Microservice: FastAPI

Browser engine: Tauri WebView (Chromium)

Steps to Reproduce

Start backend:

uvicorn main:app --host 127.0.0.1 --port 52123

Start sync microservice:

fastapi dev --port 52124

Start frontend:

npm run tauri dev

PictoPy window opens and shows:

Waiting for servers to start

After a few seconds, the window closes and the terminal logs Error 1412.

Expected Behavior

The Tauri frontend should remain open and connect to the local backend services once they are running.

Actual Behavior

Backend and sync microservice stay healthy

Frontend exits automatically

Error 1412 logged from Chromium WebView

Additional Notes

A similar warning exists for ONNX Runtime on Windows 11, which is documented as harmless.

This issue seems related to Tauri / WebView lifecycle handling on Windows 11 rather than PictoPy logic.

Documenting this behavior may help avoid confusion for Windows contributors.

### Record

- [x] I agree to follow this project's Code of Conduct