You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[P0][FIELD] Startup crashes on reopen and Waves WaveShell wrong-class confirmation #547
Milestone B triage (2026-11-17, main@d6fd94815bd0):P0 · vst3-host · defect · needs-repro. This is classification, not proof of a bug on the published alpha.26.
Boundary: Historical startup and WaveShell incident; determine reproduction on exact current public build.
Evidence-based exit criteria:
Reproduce alpha.26 startup/reopen crash or WaveShell class mismatch with WER faulting module, exact SHA, plugin IDs and ASIO/device state; distinguish the two failures.
Prove no crash loop through quarantined restore/recovery, deterministic VST3 class enumeration and native Windows regression; close only after current-build field proof.
Full prioritized issue ledger · Do not close from an old CI run; validate exact current binary or approved owner evidence as applicable.
Multiple users report repeated crashes whenever ArSonMix launches, and mismatched Waves plugin names vs actual processors. No Windows crash dump or affected build SHA has yet been supplied; do not conflate these failures.
CONFIRMED WAVES HOST ROOT: pinned JUCE 8.0.15 searches WaveShell class indices BEFORE IPluginFactory3::setHostContext. A WaveShell factory can reorder classes during setHostContext. Upstream JUCE fix 2026-09-03: juce-framework/JUCE@3fa28d0
Fix candidate: #545 HEAD e07c8e7. Fast native + Harmony DSP + UI PASS. One FAT Windows run https://github.com/masarray/arsonmix/actions/runs/42918578102 underway. It also adds an automatic VST3 startup restore crash marker, preventing infinite vendor-restore replay while preserving .smix.
FIELD TRIAGE: obtain exact ArSonMix build SHA, Windows/WebView2 version, ASIO device/driver, whether failure is before GUI, device open, plugin scan, session restore or first audio callback. Request Reliability Monitor (perfmon /rel) details, faulting DLL and WER dump/exception code; do not collect licenses or private keys.
FIELD ACCEPTANCE: licensed Waves WaveShell (including multi-class v17): selected class/name equals opened UI/DSP; ASIO audio + FX/bypass; cold start twice and last-used .smix restore; forced vendor restore crash causes second start to open GUI with preserved session, no repeated auto crash. Separately triage any launch crash outside VST3 restore. CI is not hardware FAT.
Newly implemented follow-up draft PR #549, candidate 9c636a499f9864cff3445ed35285079c6829cb9b: repairs an otherwise permanent safe-start marker after a user deliberately opens a fixed/updated VST3 session. An explicit manual Open now arms a fresh crash fence and clears it only after the graph survives its 15s stability window; a new crash still blocks automatic replay, and .smix is never deleted.
Crash faults outside vendor FX restore (WebView2, driver/DLL, installer) need actual WER faulting module, exception code, device/driver, exact build; avoid claiming one cause for all reporters.
Parent PR #545 has been safely reconciled to main@c65c695d7f70fa2a43c6e668d6b9a689462fd322; head e610bbd143d818f92b200ededccb361eb81bfeaf, mergeable, fast native/Harmony/Chromium PASS. JUCE 8.0.15 WaveShell host-context ordering and catalog UID+name disambiguation remain implemented; automatic saved-FX crash marker preserves .smix.
Pre-reconciliation exact combined C++ candidate 3a3c5e8f41cd71a474f65d78e2cc06ae9e427d7e is on Windows MSVC/full CTest #42923360681: IN_PROGRESS, result PENDING. Tree comparison over 950 entries shows the new HEAD differs only in .github/workflows/p1-windows.yml and tests/ci_workflow_efficiency_test.mjs; every C++/CMake/WaveShell patch blob remains byte-identical. The previous Waves-only FAT #42918578102 passed 84/84 CTest and generated Windows ZIP/installer but predates integrated Hotkeys.
Stacked PR #549 rebased as one new commit 1159f84a3fbc2b7101bf6b325151fda5adfb1588 on P0: fix Waves WaveShell wrong VST3 class and repeated startup FX crashes #545, only 4 files, fast native PASS. Physical Manual Open now arms crash guard before materializeLogicalFxForBinding (which can prepare vendor DLLs), then preserves marker on process crash and clears after verified 15s stability. Keeps hotkeys_.activateSession(id,&importedHotkeys), adds C++ retry/failure tests and JS ordering/Hotkey contract.
Do NOT merge parent on incomplete Windows qualification or rerun paid FAT; do NOT merge child before parent. After parent verified/merged, transplant child 4-file tree onto merged main and do one selective Windows qualification. Physical licensed Waves ASIO startup/processor identity and any non-VST3 Windows WER crash traces remain FIELD PENDING.
Milestone D exact-SHA software candidate ee7b81e444c054623c0b2c00f102516631b9c704 passed Windows FAT #44081695177, 100/100 native CTests including WavesVst3IdentityAndStartupCrashRecovery. Per-user installer and upgrade/rollback also passed. This qualifies synthetic class-identity / crash-guard regression only; does NOT prove licensed WaveShell v17 actual GUI/DSP identity, actual Windows reopen after an authentic vendor fault, or physical ASIO on field hardware. PR #756 FAT matrix retains the field steps. Keep #547 open until exact candidate owner proof (no WER/private license exposure).
Activity
masarray commentedon Nov 10, 2026
P0 milestone continuation — 2026-11-11
9c636a499f9864cff3445ed35285079c6829cb9b: repairs an otherwise permanent safe-start marker after a user deliberately opens a fixed/updated VST3 session. An explicit manual Open now arms a fresh crash fence and clears it only after the graph survives its 15s stability window; a new crash still blocks automatic replay, and.smixis never deleted.masarray commentedon Nov 10, 2026
2026-11-11 continuation checkpoint — P0 Waves & startup crash recovery
main@c65c695d7f70fa2a43c6e668d6b9a689462fd322; heade610bbd143d818f92b200ededccb361eb81bfeaf, mergeable, fast native/Harmony/Chromium PASS. JUCE 8.0.15 WaveShell host-context ordering and catalog UID+name disambiguation remain implemented; automatic saved-FX crash marker preserves .smix.3a3c5e8f41cd71a474f65d78e2cc06ae9e427d7eis on Windows MSVC/full CTest #42923360681: IN_PROGRESS, result PENDING. Tree comparison over 950 entries shows the new HEAD differs only in.github/workflows/p1-windows.ymlandtests/ci_workflow_efficiency_test.mjs; every C++/CMake/WaveShell patch blob remains byte-identical. The previous Waves-only FAT #42918578102 passed 84/84 CTest and generated Windows ZIP/installer but predates integrated Hotkeys.1159f84a3fbc2b7101bf6b325151fda5adfb1588on P0: fix Waves WaveShell wrong VST3 class and repeated startup FX crashes #545, only 4 files, fast native PASS. Physical Manual Open now arms crash guard beforematerializeLogicalFxForBinding(which can prepare vendor DLLs), then preserves marker on process crash and clears after verified 15s stability. Keepshotkeys_.activateSession(id,&importedHotkeys), adds C++ retry/failure tests and JS ordering/Hotkey contract.masarray commentedon Nov 17, 2026
Milestone D exact-SHA software candidate
ee7b81e444c054623c0b2c00f102516631b9c704passed Windows FAT #44081695177, 100/100 native CTests includingWavesVst3IdentityAndStartupCrashRecovery. Per-user installer and upgrade/rollback also passed. This qualifies synthetic class-identity / crash-guard regression only; does NOT prove licensed WaveShell v17 actual GUI/DSP identity, actual Windows reopen after an authentic vendor fault, or physical ASIO on field hardware. PR #756 FAT matrix retains the field steps. Keep #547 open until exact candidate owner proof (no WER/private license exposure).