I didn’t see a feature req post for this, so apologies if one already exists. So Bitwig has the ability to sandbox plugins, either by individual or by mfg. This increases memory usage a bit, but it also allows for graceful crashes in case a plugin goes haywire (i.e. it doesn’t take down the whole program). It helps make for an absolutely rock solid DAW. I’m still getting all the kinks worked out of my Win10 GP setup, but the last 2 nights, one plugin of mine (Z3ta 2) just randomly decided to start crashing GP whenever it would get loaded. I was using predictive loading and even though it was 3 racks down - it would crash the entire thing. Even though it worked fine for almost a month, It decided to start happening on friday night (and again last night) randomly. Fortunately the event log pointed me to that particular plugin - which I promply renamed and had to rescan the entire plugin list (in the middle of Don’t Stop Believin’ mind you) while the band played without any piano.
This same sort of thing happened to me in the beginning with OP-X Pro II - I ended up just getting rid of it and replacing the Oberheim sounds with the free OBXd (which is rock solid - albeit not quite as good). The developer basically told me that it’s a GP issue and that older versions of GP worked fine with it, but that’s a different issue. Plugin sandboxing would have saved me a ton of headache at the gig.