Description:
I am using CloakBrowser Pro Chromium `148.0.7778.215.3` and it crashes immediately on my Linux Docker runtime.
The crash happens when calling `launchPersistentContext()`. It also happens with a minimal `about:blank` test and no proxy, so this does not appear to be proxy-related.
Expected:
`launchPersistentContext()` should start Chromium and create the persistent context successfully.
Actual:
Chromium launches, then immediately exits with `SIGSEGV`.
CloakBrowser version:
- npm wrapper: `cloakbrowser@0.4.4`
- Pro binary: `148.0.7778.215.3`
Wrapper:
JavaScript / Node.js
Environment:
- Linux VPS
- Docker: yes
- Node: v22.23.1 inside container
- Platform: linux-x64
- DISPLAY: Xvfb on `:99`
- Windows fonts mounted at `/usr/share/fonts/windows`
- Widevine mounted, but not required to reproduce
Launch options:
```js
import { launchPersistentContext, binaryInfo } from "cloakbrowser";
console.log(await binaryInfo());
const ctx = await launchPersistentContext({
userDataDir: `/tmp/cb-smoke-${Date.now()}`,
headless: false,
geoip: false,
args: [
"--fingerprint=12345",
"--fingerprint-noise=false",
],
});
const page = ctx.pages()[0] || await ctx.newPage();
await page.goto("about:blank");
console.log("launch-ok");
await ctx.close();Tested with a different IP or proxy?
Yes. It fails with no proxy at all.
Works outside Docker / on host machine?
Not tested outside Docker.
Steps to reproduce:
-
Install wrapper:
npm install cloakbrowser@0.4.4
-
Use Pro binary 148.0.7778.215.3:
CLOAKBROWSER_VERSION=148.0.7778.215.3
-
Run the minimal script above inside Docker.
-
Chromium crashes immediately.
Error output:
binaryInfo {
version: '148.0.7778.215.3',
bundledVersion: '146.0.7680.177.5',
tier: 'pro',
platform: 'linux-x64',
binaryPath: '/root/.cloakbrowser/chromium-148.0.7778.215.3-pro/chrome',
installed: true,
cacheDir: '/root/.cloakbrowser/chromium-148.0.7778.215.3-pro'
}
browserType.launchPersistentContext: Target page, context or browser has been closed
Browser logs:
<launching> /root/.cloakbrowser/chromium-148.0.7778.215.3-pro/chrome ...
<launched> pid=56
Call log:
- <launched> pid=56
- [pid=56] <gracefully close start>
- [pid=56] <kill>
- [pid=56] <will force kill>
- [pid=56] exception while trying to kill process: Error: kill ESRCH
- [pid=56] <process did exit: exitCode=null, signal=SIGSEGV>
- [pid=56] starting temporary directories cleanup
- [pid=56] finished temporary directories cleanup
Additional notes:
I tested rollback with the new wrapper version pinning:
CLOAKBROWSER_VERSION=148.0.7778.215.2
The exact same script works with 148.0.7778.215.2:
So the regression appears specific to the Linux x64 Pro binary 148.0.7778.215.3.
Tested with a different IP or proxy?
Yes. It fails with no proxy at all.
Works outside Docker / on host machine?
Not tested outside Docker.
Steps to reproduce:
Install wrapper:
Use Pro binary
148.0.7778.215.3:Run the minimal script above inside Docker.
Chromium crashes immediately.
Error output:
Additional notes:
I tested rollback with the new wrapper version pinning:
The exact same script works with
148.0.7778.215.2:So the regression appears specific to the Linux x64 Pro binary
148.0.7778.215.3.