[Bug 36600] New: valgrind shows a possible leak in winhttp/tests/winhttp.c

https://bugs.winehq.org/show_bug.cgi?id=36600

Bug ID: 36600
           Summary: valgrind shows a possible leak in
                    winhttp/tests/winhttp.c
           Product: Wine
           Version: 1.7.19
          Hardware: x86
                OS: Linux
            Status: NEW
          Keywords: download, source, testcase
          Severity: normal
          Priority: P2
         Component: winhttp
          Assignee: [e-mail]
          Reporter: [e-mail]

==19459== 112 bytes in 1 blocks are possibly lost in loss record 531 of 781
==19459==    at 0x7BC4C6DF: notify_alloc (heap.c:255)
==19459==    by 0x7BC50F23: RtlAllocateHeap (heap.c:1716)
==19459==    by 0x4E24AA1: heap_alloc_zero (winhttp_private.h:325)
==19459==    by 0x4E25408: WinHttpOpen (session.c:223)
==19459==    by 0x4CB175F: test_Timeouts (winhttp.c:1113)
==19459==    by 0x4CBFCBE: func_winhttp (winhttp.c:3067)
==19459==    by 0x4CC0C75: run_test (test.h:584)
==19459==    by 0x4CC1064: main (test.h:654)
==19459==

[Bug 36600] valgrind shows a possible leak in winhttp/tests/winhttp.c

https://bugs.winehq.org/show_bug.cgi?id=36600

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |valgrind

[Bug 36600] valgrind shows a possible leak in winhttp/tests/winhttp.c

https://bugs.winehq.org/show_bug.cgi?id=36600

--- Comment #1 from Hans Leidekker  ---
test_Timeouts is clean here. Do you still see this?

[Bug 36600] valgrind shows a possible leak in winhttp/tests/winhttp.c

https://bugs.winehq.org/show_bug.cgi?id=36600

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Austin English  ---
(In reply to Hans Leidekker from comment #1)
> test_Timeouts is clean here. Do you still see this?

No, I don't. I do see a different problem though:
==18450== Invalid read of size 8
==18450==    at 0x6C04110: ??? (typelib.c:6301)
==18450==    by 0x6C04F6D: DispCallFunc (typelib.c:6807)
==18450==    by 0x6C06A25: ITypeInfo_fnInvoke (typelib.c:7165)
==18450==    by 0x674A75E: ITypeInfo_Invoke (oaidl.h:1596)
==18450==    by 0x674A75E: winhttp_request_Invoke (???:0)
==18450==    by 0x6518B57: IWinHttpRequest_Invoke (httprequest.h:371)
==18450==    by 0x6518B57: test_IWinHttpRequest_Invoke (???:0)
==18450==    by 0x651A3FE: func_winhttp (winhttp.c:4281)
==18450==    by 0x651B5E3: run_test (test.h:589)
==18450==    by 0x651BAB8: main (test.h:673)
==18450==  Address 0x7ffffe04e448 is 0 bytes after a recently re-allocated
block of size 24 alloc'd
==18450==    at 0x7BC64847: notify_alloc (heap.c:254)
==18450==    by 0x7BC69FB3: RtlAllocateHeap (heap.c:1716)
==18450==    by 0x6BEE73F: heap_alloc (typelib.h:601)
==18450==    by 0x6C04BC8: DispCallFunc (typelib.c:6756)
==18450==    by 0x6C06A25: ITypeInfo_fnInvoke (typelib.c:7165)
==18450==    by 0x674A75E: ITypeInfo_Invoke (oaidl.h:1596)
==18450==    by 0x674A75E: winhttp_request_Invoke (???:0)
==18450==    by 0x6518B57: IWinHttpRequest_Invoke (httprequest.h:371)
==18450==    by 0x6518B57: test_IWinHttpRequest_Invoke (???:0)
==18450==    by 0x651A3FE: func_winhttp (winhttp.c:4281)
==18450==    by 0x651B5E3: run_test (test.h:589)
==18450==    by 0x651BAB8: main (test.h:673)
==18450==

[Bug 36600] valgrind shows a possible leak in winhttp/tests/winhttp.c

https://bugs.winehq.org/show_bug.cgi?id=36600

Alexandre Julliard  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #3 from Alexandre Julliard  ---
Closing bugs fixed in 2.4.