Plugin Sandboxing Doesn't Work

[rickpress]

Has anyone had a situation where plugin sandboxing doesn't work on the latest stable and beta versions of waveform? If I have plugin sandboxing enabled I just get error messages saying the sandbox has crashed and can't load any plugins. Not a big deal as running waveform without sandboxing everything works but just wondered if anyone else is having this problem on windows 11? I've had a few windows updates recently and was wondering if this may be to do with it.

[vitocorleone123]

I tried enabling it after Blue Cat Audio Remote Control 2 was crashing the DAW (but not Studio One), and all it did was freeze up the DAW.

[talby]

On Linux it is working only half way: if a plugin is causing a crash, then the sandbox is crashed instead of Waveform. So far so good. This is how a sandbox protection shall work. However, the sandbox fails to become fully removed, as a clean up process. Now WF appears to be frozen, because it is waiting for the sandbox to be removed before WF would continue with the work. In this state it is needed to interfere as the user and remove the sandbox process manually! If this is done, then WF continues to work as intended, shows the message that the sandbox shut down (crashed), and that there is no more sandbox active until the user would manually restart one, including the hint how to do this.

Last time I checked for this, only the Linux version showed this bug. Linux users can manually interfere in the following way:
- search for the Waveform13 process with suffix "--__bc_id_: *"
example how the sandbox process is named: /usr/bin/Waveform13 --__bc_id_:pb889931081ef1988
- by the Linux "kill" command simply TERMINATE it (send TERM to it), no need to kill it by harder means
- do NOT kill (terminate) the initial Waveform process, which is not named with such suffix "--__bc_id_: *"

[rickpress]

Got waveform running fine now it was some settings in Comodo Internet Security Pro that were interfering with it. Thanks to comodo support it's now working fine.

[talby]

That's an interesting finding!
Glad you got it solved.

[rickpress]

Comodo uses a sandbox and sandboxes everything it doesn't know. but even with comodo turned off the sandbox still runs which I wasn't aware of turns out it was sandboxing .bat files that seem to be from tracktion and other stuff but it's working fine now.

[pough]

This is what I do based on my own experience:

1. Keep Sandboxing on
2. De-select Sandboxing for all individual plugins*
3. Turn it on for any plugin that misbehaves

Some plugins don't like to be sandboxed. Some plugins need to be sandboxed. Sometimes the sandbox will mysteriously crash even when no sandboxed plugins are running, but since no sandboxed plugins are running, it doesn't matter.

* I think you can select all plugins and then un-checking one will un-check all.