VitalRecorder 1.19.9 crashes (0xc0000409) when running any filter via Add Filter #752
I am using VitalRecorder for a research project (real-time monitoring of soda lime absorbent remaining capacity via a custom openvital filter).
I am experiencing a reproducible crash when running any filter (both built-in filters and a custom filter I wrote) through the Add Filter feature.
[Environment]
- VitalRecorder version: 1.19.9.0
- OS: Windows (hospital PC)
- openvital server: starts and lists filters normally (both built-in and custom filters load without error in the console log)
[Steps to reproduce]
1. Open a recorded .vital file in VitalRecorder
2. Go to the Filters tab and click "Add Filter"
3. Select any filter (this happens with built-in filters such as Resp - Compliance, as well as with a custom filter I placed in the openvital "filters" folder)
4. Assign input/output tracks
5. Press the play/run button
[Result]
VitalRecorder immediately crashes and restarts. The filter configuration is lost after the restart. This happens 100% of the time, with no error shown in the openvital server console (the command-prompt window running "python.exe -m openvital" shows no traceback at the time of the crash).
[Windows Event Viewer details]
- Log Name: Application
- Source: Application Error
- Event ID: 1000
- Faulting application: Vital.exe, version 1.19.9.0
- Faulting module: Vital.exe, version 1.19.9.0 (same as the application itself, not an external DLL)
- Exception code: 0xc0000409 (STATUS_STACK_BUFFER_OVERRUN)
- Fault offset: 0x00000000007dbbcd
- Faulting application path: C:\Users\me\AppData\Local\VitalRecorder\Vital.exe
Since the crash occurs identically with both official filters and a custom filter (and the openvital server itself shows no errors when listing/loading filters), this appears to be an issue in VitalRecorder's filter-execution code path rather than in my filter script or environment setup.
I would be happy to provide the full Windows Event Viewer XML, the .vital file used for testing, or my custom filter script if that would help reproduce and fix this issue. Please let me know if there is a workaround, or if a fix is planned in an upcoming release.
Thank you for maintaining this valuable open-source tool.