libuv使用不当导致的内存泄漏

libuv库使用过程中，发现简单的定时器不关闭对应的句柄会导致内存泄漏；使用文章后面的测试代码缺少uv_close或者uv_loop_close均会导致内存泄漏，关闭的时机也有影响。

Detected memory leaks!
Dumping objects ->
{185} normal block at 0x00FB7860, 32 bytes long.
Data: < R z > E8 52 E8 7A 00 00 00 00 00 00 00 00 00 00 00 00
{184} normal block at 0x00FB7818, 8 bytes long.
Data: < > 00 00 00 00 00 00 00 00
{183} normal block at 0x00FB77A8, 48 bytes long.
Data: < > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Object dump complete.

使用VS2010进行调试
1 设置项目依赖

2 添加泄漏位置的断点
_CrtSetBreakAlloc(185);
根据泄漏报告的位置确定，本例中有3处泄漏， 185， 184， 183，需要调试3次

3 调试代码
打开调用堆栈，发现这里分配的内存4 * 8刚好32字节
uv_default_loop
->uv_loop_init
->uv__loops_add
->uv__realloc

而这块内存是在uv_loop_close->uv__loop_close->uv__loops_remove中释放的。

同样的方法把分两次设置新的断点位置_CrtSetBreakAlloc(184);_CrtSetBreakAlloc(183);
发现uv_loop_init中有其他两处内存分配

loop->timer_heap = timer_heap = uv__malloc(sizeof(*timer_heap));

lfields = (uv__loop_internal_fields_t*) uv__calloc(1, sizeof(*lfields<