Chrome closes itself immediately after vite launches it

[CCRcmcpe]

Reproduce steps:

1. Use latest Chrome Canary, specific version below. Violentmonkey 2.35.0, latest as of I write.
2. Use this .env file to allow MV2:

BROWSER=chrome
BROWSER_ARGS="--enable-features=AllowLegacyMV2Extensions --disable-features=ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled,ExtensionsManifestV3Only"

3. npm run dev.
4. Watch Chrome closes itself after briefly displaying this, as if Violentmonkey is not enabled:

I say "close", because there's nothing in chrome://crashes.
Alternatively you can open the url (e.g. http://127.0.0.1:5173/) while vite dev server is running from command line.

chrome.exe --enable-features=AllowLegacyMV2Extensions --disable-features=ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled,ExtensionsManifestV3Only http://127.0.0.1:5173/

Opening the url by launching chrome manually does work and opens the Violentmonkey install page. Only the command line does not work, weirdly. I don't know if this is Violentmonkey specific , but this vite plugin should support Violentmonkey.

Chrome version detail:
Google Chrome 148.0.7767.0 (Official Build) canary (64-bit) (cohort: Clang-64)
Revision 009218e3d55b4b6f3ddce99febc41344ad058c2f-refs/branch-heads/7767@{#1}
OS Windows 11 Version 25H2 (Build 26200.8037)

[CCRcmcpe]

This does not happen with the Edge, which does not have the MV3 crap.

Microsoft Edge 146.0.3856.84 (正式版本) (64 位)
修订 fe100ed2d0fb16c7e2cbfdc67778768309f50170
Chromium 版本 146.0.7680.166