[xcb] Unknown sequence number while processing reply #70

New Issue

grin · 2021-06-29T15:19:36Z

grin commented

2021-06-29 15:19:36 +00:00

Debian/Linux, desktop client, amd64, xorg, xfce.

Client crashed after a day with the very polite apology:

[xcb] Unknown sequence number while processing reply
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
cwtch: ../../src/xcb_io.c:725: _XReply: Assertion `!xcb_xlib_threads_sequence_lost' failed.

Debian/Linux, desktop client, amd64, xorg, xfce. Client crashed after a day with the very polite apology: ``` [xcb] Unknown sequence number while processing reply [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. cwtch: ../../src/xcb_io.c:725: _XReply: Assertion `!xcb_xlib_threads_sequence_lost' failed. ```

sarah added the

bug

label 2021-06-29 16:29:48 +00:00

sarah added the

flutter

label 2021-06-29 17:03:34 +00:00

sarah commented

2021-06-29 17:05:51 +00:00

Thanks for reporing!

Dived into this a little this morning, some notes:

I found one reference to this trace in Flutter engine repo:

https://github.com/flutter/engine/pull/21796

Which points to https://github.com/flutter/engine/pull/21831/files as a solution.

However both of those issues predate our use of Flutter so it's unlikely we have older flutter-generated C++ code causing this.

Next steps:

Check our auto-generated linux code against the latest flutter engine version to see if there are any obvious issues.
Attempt to replicate this bug, to see if we can make it consistent enough to identify the cause and/or file an issue with flutter.

Thanks for reporing! Dived into this a little this morning, some notes: I found one reference to this trace in Flutter engine repo: * https://github.com/flutter/engine/pull/21796 Which points to https://github.com/flutter/engine/pull/21831/files as a solution. However both of those issues predate our use of Flutter so it's unlikely we have older flutter-generated C++ code causing this. Next steps: * Check our auto-generated linux code against the latest flutter engine version to see if there are any obvious issues. * Attempt to replicate this bug, to see if we can make it consistent enough to identify the cause and/or file an issue with flutter.

sarah added this to the Cwtch Beta 1.1 project 2021-06-29 17:06:05 +00:00

sarah added the

need-replication-or-investigation

label 2021-06-29 17:06:10 +00:00

sarah added the

cwtch-beta-1.1

label 2021-07-13 17:49:09 +00:00

sarah removed this from the Cwtch Beta 1.1 project 2021-07-13 20:10:59 +00:00

sarah removed the

cwtch-beta-1.1

label 2021-07-13 20:11:02 +00:00

sarah commented