please take a deep breath and start pinning which ones are systematic problem troublers and which part of it's to blame--as i think i said you before (eg. re. abGate), their fancy GUIs are often a source of crappy behavior.
however there are a (few) standard and stable ones which shall be considered rock solid. though. nevertheless.
if you're not finding any of those, that is, everything is troublesome on your perspective, then you/we must start to investigate why--as proverbial as it sounds, YMMV.
there's no doubt things do depend on a whole lot on here, where, how and who made the packaging and building. in other words, do you have a tight, trusted and secured stable system or is it a heap stack of a scrapyard every now and then? :)
first thing to ask (yourself) is, where did you get those plugins in the first place? are they fit to the system environment you're working on? what is your base distro? did you compile everything from source or did you installed all related packages from one single and trusty distro packager?
are you running a debug build of qtractor (./configure --enable-debug ...)? if not, try so. then, on each segfault you encounter, look at the stacktrace that is left behind on the console/terminal--that should help you/we find what to blame, whether a rogue plugin or qtractor itself:)
don't despair! :)
which plugins are giving you the (head)aches ?
please take a deep breath and start pinning which ones are systematic problem troublers and which part of it's to blame--as i think i said you before (eg. re. abGate), their fancy GUIs are often a source of crappy behavior.
however there are a (few) standard and stable ones which shall be considered rock solid. though. nevertheless.
if you're not finding any of those, that is, everything is troublesome on your perspective, then you/we must start to investigate why--as proverbial as it sounds, YMMV.
there's no doubt things do depend on a whole lot on here, where, how and who made the packaging and building. in other words, do you have a tight, trusted and secured stable system or is it a heap stack of a scrapyard every now and then? :)
first thing to ask (yourself) is, where did you get those plugins in the first place? are they fit to the system environment you're working on? what is your base distro? did you compile everything from source or did you installed all related packages from one single and trusty distro packager?
are you running a debug build of qtractor (./configure --enable-debug ...)? if not, try so. then, on each segfault you encounter, look at the stacktrace that is left behind on the console/terminal--that should help you/we find what to blame, whether a rogue plugin or qtractor itself:)
have fun && cheers