[xcb] Unknown sequence number while processing reply #70

Closed
opened 1 year ago by grin · 2 comments
grin commented 1 year ago

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 1 year ago
sarah added the
flutter
label 1 year ago
Owner

Thanks for reporing!

Dived into this a little this morning, some notes:

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

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 1 year ago
sarah added the
need-replication-or-investigation
label 1 year ago
sarah added the
cwtch-beta-1.1
label 12 months ago
sarah removed this from the Cwtch Beta 1.1 project 12 months ago
sarah removed the
cwtch-beta-1.1
label 12 months ago
Owner

Assume this was fixed in the lead up to Flutter 3 as I've not seen it reported recently.

If it reappears in Nightly / 1.8 we will dig in further.

Assume this was fixed in the lead up to Flutter 3 as I've not seen it reported recently. If it reappears in Nightly / 1.8 we will dig in further.
sarah closed this issue 2 weeks ago
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.