Open avojak opened 2 years ago
Saw the application crash with the following messages in the log:
(com.github.avojak.iridium:2): GLib-Net-DEBUG: 09:59:01.094: CLIENT[0x559e4edf6a60]: yielding operation OP_READ (com.github.avojak.iridium:2): GLib-Net-DEBUG: 09:59:01.094: CLIENT[0x559e4edf6a60]: successfully read 85 bytes from TLS connection ** (com.github.avojak.iridium:2): DEBUG: 09:59:01.095: ServerConnection.vala:336: :molten!~molt@178-222-245-206.static.isp.telekom.rs QUIT :Ping timeout: 240 seconds\u000d (com.github.avojak.iridium:2): GLib-Net-DEBUG: 09:59:01.095: CLIENT[0x559e4edf6a60]: starting to read data from TLS connection (com.github.avojak.iridium:2): GLib-Net-DEBUG: 09:59:01.095: CLIENT[0x559e4edf6a60]: claiming operation OP_READ (com.github.avojak.iridium:2): GLib-Net-DEBUG: 09:59:01.095: CLIENT[0x559e4edf6a60]: claiming operation OP_READ succeeded ** (com.github.avojak.iridium:2): WARNING **: 09:59:01.095: MainLayout.vala:471: No chat view exists for irc.libera.chat, molten (com.github.avojak.iridium:2): GLib-Net-DEBUG: 09:59:01.623: CLIENT[0x559e4edf6a60]: yielding operation OP_READ (com.github.avojak.iridium:2): GLib-Net-DEBUG: 09:59:01.624: CLIENT[0x559e4edf6a60]: successfully read 59 bytes from TLS connection ** (com.github.avojak.iridium:2): DEBUG: 09:59:01.624: ServerConnection.vala:336: :mrfb!~MrFooBar@gateway/tor-sasl/mrfb QUIT :Quit: leaving\u000d (com.github.avojak.iridium:2): GLib-Net-DEBUG: 09:59:01.624: CLIENT[0x559e4edf6a60]: starting to read data from TLS connection (com.github.avojak.iridium:2): GLib-Net-DEBUG: 09:59:01.624: CLIENT[0x559e4edf6a60]: claiming operation OP_READ (com.github.avojak.iridium:2): GLib-Net-DEBUG: 09:59:01.624: CLIENT[0x559e4edf6a60]: claiming operation OP_READ succeeded ** ERROR:linkedlist.c:691:gee_linked_list_real_get: assertion failed: (index < this._size) Bail out! ERROR:linkedlist.c:691:gee_linked_list_real_get: assertion failed: (index < this._size)
My first guess would be to look into how the list of users is maintained and updated, since this seems to have happened after a user quit.
Unable to reproduce the issue. Will kick it out of the 1.8.0 release but leave open in case it happens again.
Saw the application crash with the following messages in the log:
My first guess would be to look into how the list of users is maintained and updated, since this seems to have happened after a user quit.