[Libwebsockets] [libwebsockets] #111: Assertion `0' problem

Trac trac at libwebsockets.org
Wed Apr 15 22:37:34 CEST 2015

#111: Assertion `0' problem
  Reporter:  marcin                 |      Owner:  marcin
      Type:  defect                 |     Status:  new
  Priority:  major                  |  Milestone:
 Component:  libwebsockets library  |    Version:
Resolution:                         |   Keywords:

Comment (by agreen):

 The assert() is there to catch the situation we have some of your old
 write still pending, but for some reason a new write was requested.  Lws
 should not let the user code have a WRITEABLE callback until it managed to
 flush your remaining pending write.

 To understand what caused it you need to run the server under gdb and
 reproduce it... when the asset fires you can get a backtrace that will
 tell who is trying to send something new.

 Also make sure you have latest lws git.

Ticket URL: <http://libwebsockets.org/trac/libwebsockets/ticket/111#comment:1>
libwebsockets <http://libwebsockets.org>
libwebsockets C library

More information about the Libwebsockets mailing list