#78: c2s crash
---------------------+------------------------------------------------------
Reporter: tofu | Owner: smoku
Type: defect | Status: new
Priority: critical | Component: c2s
Version: 2.1 | Resolution:
Keywords: | Blocking:
---------------------+------------------------------------------------------
Comment (by jack):
I looked into this a bit, and it appears some corruption is happening
somewhere. _sx_buffer_new is called with (NULL, 1024, NULL, NULL), yet
the backtrace shows len as 14. Also, there is no reason the malloc should
fail.
Memory use at the time of this crash was 4GB available (out of 8GB total).
CPU load was quite high when this happened. This is a dual quad-core
machine, and the 5m average load before the spike was about 1. At the
time of the crash it was just under 5.
I'm not sure if the load was caused by c2s or one of our other server
components, but it seems suspicious.
--
Ticket URL: <http://jabberd2.xiaoka.com/ticket/78#comment:2>
jabberd2 <http://jabberd2.xiaoka.com/>
jabberd2 project
_______________________________________________
jabberd2 mailing list
[email protected]
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
