#25962 closed defect (worksforme)

Tor Browser crash: [xcb] Unknown sequence number while processing queue

Reported by: cypherpunks Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-crash
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Happened after I switched to Lubuntu (latest LTS, latest Tor Browser alpha 64),

[notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
firefox: ../../src/xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
[Child 4116] WARNING: pipe error (3): Connection reset by peer: file /var/tmp/build/firefox-90e16dd25b6e/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 322
[Child 4116] ###!!! ABORT: Aborting on channel error.: file /var/tmp/build/firefox-90e16dd25b6e/ipc/glue/MessageChannel.cpp, line 2152
[Child 4116] ###!!! ABORT: Aborting on channel error.: file /var/tmp/build/firefox-90e16dd25b6e/ipc/glue/MessageChannel.cpp, line 2152
[notice] Owning controller connection has closed -- exiting now.
[notice] Catching signal TERM, exiting cleanly.
./start-tor-browser: line 372:  4023 Aborted                 (core dumped) TOR_CONTROL_PASSWD=${TOR_CONTROL_PASSWD} ./firefox --class "Tor Browser" -profile TorBrowser/Data/Browser/profile.default "${@}" < /dev/null

Child Tickets

Change History (9)

comment:1 Changed 20 months ago by cypherpunks

Happens a lot unfortunately, and can be triggered by opening up a lot of links in new tabs (go to news.ycombinator.com for example and start opening up all of the links there in new tabs consecutively until it crashes).

Edit: Yet another crash,

[notice] New control connection opened from 127.0.0.1.
[notice] New control connection opened from 127.0.0.1.
Gtk-Message: Failed to load module "overlay-scrollbar"
Fontconfig warning: "/home/debian/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 145: blank doesn't take any effect anymore. please remove it from your fonts.conf
(firefox:6146): Gtk-CRITICAL **: IA__gtk_clipboard_set_with_data: assertion 'targets != NULL' failed
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
firefox: ../../src/xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
###!!! [Child][MessageChannel] Error: (msgtype=0x3E0003,name=PCompositable::Msg_Destroy) Channel error: cannot send/recv
###!!! [Child][MessageChannel] Error: (msgtype=0xE00003,name=PTexture::Msg_Destroy) Channel error: cannot send/recv
###!!! [Child][MessageChannel] Error: (msgtype=0xE00003,name=PTexture::Msg_Destroy) Channel error: cannot send/recv
###!!! [Child][MessageChannel] Error: (msgtype=0x3E0003,name=PCompositable::Msg_Destroy) Channel error: cannot send/recv
###!!! [Child][MessageChannel] Error: (msgtype=0xE00003,name=PTexture::Msg_Destroy) Channel error: cannot send/recv
###!!! [Child][MessageChannel] Error: (msgtype=0xE00003,name=PTexture::Msg_Destroy) Channel error: cannot send/recv
###!!! [Child][MessageChannel] Error: (msgtype=0x3E0003,name=PCompositable::Msg_Destroy) Channel error: cannot send/recv
###!!! [Child][MessageChannel] Error: (msgtype=0xE00003,name=PTexture::Msg_Destroy) Channel error: cannot send/recv
###!!! [Child][MessageChannel] Error: (msgtype=0xE00003,name=PTexture::Msg_Destroy) Channel error: cannot send/recv
###!!! [Child][MessageChannel] Error: (msgtype=0x3E0003,name=PCompositable::Msg_Destroy) Channel error: cannot send/recv
###!!! [Child][MessageChannel] Error: (msgtype=0xE00003,name=PTexture::Msg_Destroy) Channel error: cannot send/recv
###!!! [Child][MessageChannel] Error: (msgtype=0xE00003,name=PTexture::Msg_Destroy) Channel error: cannot send/recv
###!!! [Child][MessageChannel] Error: (msgtype=0x3E0003,name=PCompositable::Msg_Destroy) Channel error: cannot send/recv
###!!! [Child][MessageChannel] Error: (msgtype=0x3E0003,name=PCompositable::Msg_Destroy) Channel error: cannot send/recv
###!!! [Child][MessageChannel] Error: (msgtype=0xE00003,name=PTexture::Msg_Destroy) Channel error: cannot send/recv
###!!! [Child][MessageChannel] Error: (msgtype=0xE00003,name=PTexture::Msg_Destroy) Channel error: cannot send/recv
###!!! [Child][MessageChannel] Error: (msgtype=0x3E0003,name=PCompositable::Msg_Destroy) Channel error: cannot send/recv
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=1709.57) [GFX1-]: Receive IPC close with reason=AbnormalShutdown
[notice] Owning controller connection has closed -- exiting now.
[notice] Catching signal TERM, exiting cleanly.
[Child 6266] WARNING: pipe error (3): Connection reset by peer: file /var/tmp/build/firefox-90e16dd25b6e/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 322
[Child 6266] ###!!! ABORT: Aborting on channel error.: file /var/tmp/build/firefox-90e16dd25b6e/ipc/glue/MessageChannel.cpp, line 2152
[Child 6266] ###!!! ABORT: Aborting on channel error.: file /var/tmp/build/firefox-90e16dd25b6e/ipc/glue/MessageChannel.cpp, line 2152
./start-tor-browser: line 372:  6146 Aborted                 (core dumped) TOR_CONTROL_PASSWD=${TOR_CONTROL_PASSWD} ./firefox --class "Tor Browser" -profile TorBrowser/Data/Browser/profile.default "${@}" < /dev/null
Last edited 20 months ago by cypherpunks (previous) (diff)

comment:2 Changed 20 months ago by gk

Status: newneeds_information

I wonder if that's https://bugzilla.mozilla.org/show_bug.cgi?id=1336745. Does this happen with a vanilla Firefox ESR 52 as well? (see: https://www.mozilla.org/en-US/firefox/organizations/all/)

comment:3 in reply to:  2 Changed 20 months ago by cypherpunks

Resolution: wontfix
Status: needs_informationclosed

Replying to gk:

I wonder if that's https://bugzilla.mozilla.org/show_bug.cgi?id=1336745. Does this happen with a vanilla Firefox ESR 52 as well? (see: https://www.mozilla.org/en-US/firefox/organizations/all/)

Yes, so this is Mozilla's business.

comment:4 Changed 20 months ago by gk

Resolution: wontfix
Status: closedreopened

Thanks for reporting back. Does anyone know how to reproduce this problem reliably? Like, what environment does one need to have to hit this issue? We could then bisect the offending commit and help Mozilla with a fix (which we would backport for Tor Browser until we pick it up).

comment:5 Changed 20 months ago by gk

Status: reopenedneeds_information

comment:6 in reply to:  4 ; Changed 20 months ago by cypherpunks

Status: needs_informationnew

Replying to gk:

We could then bisect the offending commit and help Mozilla with a fix (which we would backport for Tor Browser until we pick it up).

lol you're too kind :P I expected that you wouldn't care much in view of the ton of work that you have.

Does anyone know how to reproduce this problem reliably? Like, what environment does one need to have to hit this issue?

I hit that after a transition from Ubuntu 17.10 -> Ubuntu 18.04 -> Lubuntu 18.04 where I messed up and ended up breaking and deleting many packages, I didn't even have zlibc installed (after installing it the problem didn't happen - so far), so I guess remove zlibc and something else if needed and do the procedure I described in comment:1.

comment:7 in reply to:  6 Changed 20 months ago by cypherpunks

Replying to cypherpunks:

I hit that after a transition from Ubuntu 17.10 -> Ubuntu 18.04 -> Lubuntu 18.04 where I messed up and ended up breaking and deleting many packages, I didn't even have zlibc installed (after installing it the problem didn't happen - so far), so I guess remove zlibc and something else if needed and do the procedure I described in comment:1.

Actually it still happens even with zlibc, maybe it's some other package(s)...

comment:8 Changed 19 months ago by cypherpunks

Seems to happen with Lubuntu only, with Xfce it never crashed....

comment:9 Changed 18 months ago by cypherpunks

Resolution: worksforme
Status: newclosed

Seems to no longer happen with 8.0a9.

Note: See TracTickets for help on using tickets.