Re: libsoup websocket server memory problems

[Claudio Saavedra <csaavedra gnome org>]

On Wed, 2020-01-15 at 16:56 +0100, Benjamin Reikowski wrote:
> Hello Claudio,
>
> thank you for the fast response! As requested, the GDB backtraces
> with
> G_MESSAGES_DEBUG=all
>
> (gdb) run
> Starting program: /home/benjamin/Downloads/spielwiese/main
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> ** Message: 16:38:23.430: ws server started
> ** Message: 16:38:26.434: websocket_client_connect_cb
> (process:24969): libsoup-DEBUG: 16:38:27.582: stopping input source

This removes the input source.

> (process:24969): libsoup-DEBUG: 16:38:27.582: received control frame
> 8 with
> 0 payload
> (process:24969): libsoup-DEBUG: 16:38:27.582: responding to close
> request
> (process:24969): libsoup-DEBUG: 16:38:27.582: sent frame
> (process:24969): libsoup-DEBUG: 16:38:27.582: closing io stream
> [New Thread 0x7ffff6a4d700 (LWP 24977)]
> (process:24969): libsoup-DEBUG: 16:38:27.583: queued 8 frame of len 4
> (process:24969): libsoup-DEBUG: 16:38:27.584: waiting 5 seconds for
> peer to
> close io
> (process:24969): libsoup-DEBUG: 16:38:27.584: closed: completed io
> stream
> close
> ** Message: 16:38:27.584: websocket_client_closed_cb
> **
> libsoup:ERROR:../libsoup/soup-websocket-
> connection.c:1445:soup_websocket_connection_finalize:
> assertion failed: (!pv->input_source)
> Bail out!

So this assertion here is most likely not needed anymore. This looks
like a bug.

Claudio