(In reply to Ruediger Oertel from comment #22) > just stumbled across this one: > https://salsa.debian.org/chromium-team/chromium/-/commit/ > e9a877c236209d8700f9adf6e58ead3fb6be01a9 > > I guess we might have to go the same way ... I flagged this last time around Cr123 I think, if libstdc++ doesn't work, this package is dropped. Using libc++ means no unbundling (aka no benefit to users) and that message for Debian pretty much confirms Google playing hard and fast with memory allocation which poses a major security risk unless this is actually libstdc++ misbehaving internally. We'd have to keep chromedriver for openQA. Callum