Open Manouchehri opened 4 months ago
Does your workload work with record -n
?
My workload is different from @Manouchehri but for me that does fix it. (it also slows things down enough that they time out, but that's a separate issue..)
I tried to reproduce this but it worked for me. Chromium revision 36986813ab32b467a9f041f65bc3cd889fe8beab, args.gn
:
use_remoteexec=true
enable_nacl = false
Basically the same command line as https://github.com/rr-debugger/rr/issues/3786#issue-2411864904:
rr record ./out/Default/chrome --user-data-dir=/tmp/.chrome-user-1 --disable-crash-reporter --no-report-upload --js-flags="--expose-gc --allow-natives-syntax" --allow-running-insecure-content --allow-insecure-localhost --ignore-certificate-errors --disable-breakpad --enable-logging=stderr --v=0 --allow-sandbox-debugging --disable-gpu-sandbox --disable-seccomp-filter-sandbox --disable-setuid-sandbox --disable-namespace-sandbox --no-sandbox --disable-gpu-process-crash-limit --headless=new --timeout=5000 --dump-dom --disable-hang-monitor --vmodule=render_frame_impl=1 "https://example.com"
rr revision 172b24cb88e0a1a65238406f5174c323da8e9635.
This only seems to happen with the new headless mode, not sure what's going on. The crash does not happen when running without rr.
Backtrace: