Project

General

Profile

Actions
Copy link

Bug #11467

closed

Memory leak in win32 signal init

Bug #11467: Memory leak in win32 signal init

Added by scorpion007 (Alex Budovski) about 10 years ago. Updated over 6 years ago.

Status:
Closed
Assignee:
-
Target version:
-
ruby -v:
master
Backport:
2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
[ruby-core:<unknown>]

Description

244 bytes leaked.

+ 244 ( 244 - 0) 1 allocs	BackTrace9C86044B + 1 ( 1 - 0)	BackTrace9C86044B	allocations	ntdll!RtlpCallInterceptRoutine+40 (d:\blue\minkernel\ntos\rtl\heappriv.h, 3625)	ntdll!RtlAllocateHeap+79836 (d:\blue\minkernel\ntos\rtl\heap.c, 1892)	MSVCR120D!_heap_alloc_base+5D (f:\dd\vctools\crt\crtw32\heap\malloc.c, 58)	MSVCR120D!_heap_alloc_dbg_impl+27B (f:\dd\vctools\crt\crtw32\misc\dbgheap.c, 431)	MSVCR120D!_nh_malloc_dbg_impl+39 (f:\dd\vctools\crt\crtw32\misc\dbgheap.c, 239)	MSVCR120D!_nh_malloc_dbg+49 (f:\dd\vctools\crt\crtw32\misc\dbgheap.c, 302)	MSVCR120D!_malloc_dbg+39 (f:\dd\vctools\crt\crtw32\misc\dbgheap.c, 160)	MSVCR120D!signal+270 (f:\dd\vctools\crt\crtw32\misc\winsig.c, 346)	rubyprov!ruby_signal+38 (e:\dev\ruby\signal.c, 649)	rubyprov!install_sighandler+1B (e:\dev\ruby\signal.c, 1338)	rubyprov!Init_signal+191 (e:\dev\ruby\signal.c, 1468)	rubyprov!rb_call_inits+9A (e:\dev\ruby\inits.c, 49)	rubyprov!ruby_setup+C6 (e:\dev\ruby\eval.c, 63)

Related issues 1 (0 open — 1 closed)

Updated by jeremyevans0 (Jeremy Evans) over 6 years ago Actions
Copy link
 #1

  • Related to Bug #11468: Two mutexes leaked in Init_Thread added

Updated by jeremyevans0 (Jeremy Evans) over 6 years ago Actions
Copy link
 #2 [ruby-core:93522]

  • Status changed from Open to Feedback

Init_signal is only called once at startup. It appears the memory allocation here happens inside signal, in the MS C runtime. Does Windows provide a way to free such memory?

Updated by jeremyevans0 (Jeremy Evans) over 6 years ago Actions
Copy link
 #3

  • Status changed from Feedback to Closed
Actions
Copy link

Also available in: PDF Atom