vscode: VSCode not starting unless --no-sandbox provided in certain cases

downloaded & installed the latest insider version “code-insider-1568700490.tar.gz” and found it crashed at launch with error message:

…/code-insiders: /lib64/libdbus-1.so.3: no version information available (required by …/code-insiders)

my system: CentOS Linux release 7.4.1708 (Core)

it worked last Friday with the version “code-insider-1568277818.tar.gz”

Steps to Reproduce:

Does this issue occur when all extensions are disabled?: Yes/No

About this issue

Known workarounds on the user side:

Passing --no-sandbox argument.
Persistent but system-wide workaround is enabling a User Namespaces: sudo sysctl kernel.unprivileged_userns_clone=1 (it’s for example enabled by default on Ubuntu, but not on Arch Linux).
Enabling SUID/fallback sandbox by executing chown root chrome-sandbox && chmod 4755 chrome-sandbox (sudo might be needed).

Known solutions on the code side:

For AppImage: repackaging the app in order to hardcode the --no-sandbox arg in respective AppRun script.
For Snap: recent electron-builder versions already hardcode --no-sandbox arg for you.
For other/non-containerized package types: running chown root chrome-sandbox && chmod 4755 chrome-sandbox before preparing the packages. Depending on the repository type there also will be a need to do the same in the reporitory-related scripts, like done here for AUR.
Well, using own preloader that will pass the --no-sandbox argument for all the package types.