#80: Jabberd's memory management doesn't deal with OOM cases
------------------------+---------------------------------------------------
Reporter: sxw | Owner: smoku
Type: enhancement | Status: new
Priority: minor | Component: General
Version: 2.2 | Resolution:
Keywords: | Blocking:
------------------------+---------------------------------------------------
Changes (by smoku):
* version: 2.1 => 2.2
* type: defect => enhancement
Comment:
Rethinking this...
Exiting gracefully does not really help with OOM handling. It's a runtime
ERROR and should be handled like an error. Dumped core on failure at least
gives some backtrace and hints why the OOM happened. Gracefull exit with
one line in the log - doesn't.
Maybe we just should catch all the core dumping signals (ABRT, SEGV, ILL,
etc.), log a line in logfile that this happened and exit ungracefully
dumping the core?
--
Ticket URL: <http://jabberd2.xiaoka.com/ticket/80#comment:2>
jabberd2 <http://jabberd2.xiaoka.com/>
jabberd2 project
_______________________________________________
jabberd2 mailing list
[email protected]
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
