Bug #220

Views memory leak on tpcall on view

Added by Madars over 6 years ago. Updated over 6 years ago.

Status:NewStart date:09/21/2017
Priority:Normal (Code 4)Due date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

tested on Go runtime

==23688==  Address 0x6272a34 is 12 bytes before a block of size 64 alloc'd
==23688==    at 0x4C2ABAF: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==23688==    by 0x506BBB4: ndrx_tprealloc (typed_buf.c:305)
==23688==    by 0x50716E0: VIEW_prepare_incoming (typed_view.c:615)
==23688==    by 0x5069036: ndrx_tpgetrply (tpcall.c:793)
==23688==    by 0x506958B: ndrx_tpcall (tpcall.c:915)
==23688==    by 0x50616C5: tpcall (atmi.c:224)
==23688==    by 0x50A3F4E: Otpcall (oatmi.c:263)
==23688==    by 0x489466: _cgo_58ec266a0f9d_Cfunc_Otpcall (atmi.go:419)
==23688==    by 0x45749F: runtime.asmcgocall (/usr/src/runtime/asm_amd64.s:590)
==23688==    by 0x4077FC: runtime.cgocall (/usr/src/runtime/cgocall.go:115)
==23688==    by 0x712DFF: ??? (in /home/mvitolin/projects/endurox-go/tests/10_views/bin/client)
==23688==    by 0xFFEFFF66F: ???
==23688== 

History

#1 Updated by Madars over 6 years ago

  • Description updated (diff)

#2 Updated by Madars over 6 years ago

Seems we need to test case when response buffer is larger than source buffer (sent in service request)

#3 Updated by Madars over 6 years ago

  • Tracker changed from Feature to Bug

Also available in: Atom PDF