Hello,
i found that browsing heise[.]de crashes TBB in at least the following configurations:
- Up-To-Date TBB 14.0.1 desktop on debian-12 on a QubesOS 4.2.3 system
- Up-To-Date whonix-workstation-17-dvm on a QubesOS 4.2.3 system
- Up-To-Date whonix-workstation-17-dvm on another QubesOS 4.2.3 system
Usually within minutes of normal browsing. Often without imminent user interaction, sometimes exactly when blocking requests in a noscript popup.
All Tor Browsers with enabled scripts (Security level: Standard, Safer). This does not appear to happen on the safest level.
This started a few months ago and multiple updates did not fix this. heise[.]de is the only website i found that behaves this way. Other browsers do not seem affected.
This is what i called to troubleshoot TBB on a debian-12 qube:
user@tbbcrash:~/tor-browser/Browser$ ./start-tor-browser --log ~/crashlog3 --debug
user@tbbcrash:~$ cat crashlog3
ATTENTION: default value of option mesa_glthread overridden by environment.
[Parent 4292, IPC I/O Parent] WARNING: process 6380 exited on signal 11: file /var/tmp/build/firefox-6cf7a54847d7/ipc/chromium/src/base/process_util_posix.cc:335
Exiting due to channel error.
Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=8.38518) [GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=38.1126) [GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown
Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=6.68514) [GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=8.22036) Exiting due to channel error.
Here is a syslog of one crash:
Oct 31 10:23:27 tbbcrash rtkit-daemon[1124]: Supervising 1 threads of 1 processes of 1 users.
Oct 31 10:23:29 tbbcrash rtkit-daemon[1124]: Supervising 1 threads of 1 processes of 1 users.
Oct 31 10:23:29 tbbcrash rtkit-daemon[1124]: Supervising 1 threads of 1 processes of 1 users.
Oct 31 10:23:29 tbbcrash rtkit-daemon[1124]: Supervising 1 threads of 1 processes of 1 users.
Oct 31 10:23:29 tbbcrash rtkit-daemon[1124]: Supervising 1 threads of 1 processes of 1 users.
Oct 31 10:23:30 tbbcrash kernel: Isolated Web Co[6380]: segfault at 0 ip 00007a92fde47a70 sp 00007fffb6d84ef0 error 4 in libxul.so[7a92fb3d4000+5733000] likely on CPU 0 (core 0, socket 0)
Oct 31 10:23:30 tbbcrash kernel: Code: ff 48 83 c7 28 48 89 de e8 0d 03 03 fe 48 8b 43 38 49 89 47 60 0f 10 43 28 41 0f 11 47 50 4c 89 ff e8 14 98 99 fd 49 8b 7e 18 <48> 8b 07 48 8b 40 28 4c 89 fe 31 d2 48 83 c4 08 5b 41 5c 41 5e 41
Oct 31 10:23:49 tbbcrash sudo[6465]: user : TTY=pts/3 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/journalctl -f
Oct 31 10:23:49 tbbcrash sudo[6465]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Oct 31 10:23:58 tbbcrash sudo[6465]: pam_unix(sudo:session): session closed for user root
Please let me know if you need any additional information. Also any help to further troubleshoot would be welcome as i am unfortunately not a developer.