[Bug 26104] New: oleaut32/safearray shows a memory leak according to valgrind

http://bugs.winehq.org/show_bug.cgi?id=26104

Summary: oleaut32/safearray shows a memory leak according to
                    valgrind
           Product: Wine
           Version: 1.3.13
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Keywords: download, source, testcase
          Severity: minor
          Priority: P2
         Component: oleaut32
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

40 bytes in 1 blocks are definitely lost 
    at  notify_alloc (heap.c:254)
    by  RtlAllocateHeap (heap.c:1701)
    by  SAFEARRAY_Malloc (safearray.c:94)
    by  SafeArrayAllocData (safearray.c:539)
    by  SAFEARRAY_Create (safearray.c:235)
    by  SafeArrayCreate (safearray.c:579)
    by  test_safearray (safearray.c:583)
    by  func_safearray (safearray.c:1813)
    by  run_test (test.h:556)
    by  main (test.h:624)

[Bug 26104] oleaut32/safearray shows a memory leak according to valgrind

http://bugs.winehq.org/show_bug.cgi?id=26104

--- Comment #1 from Nikolay Sivov  2011-02-14 17:41:36 CST ---
We're calling SafeArrayDestroyDescriptor without freeing data before that, so a
leak is probably justified in this case.

Actually we need some tests for that showing that internally allocated memory
is not freed and still accessible.

[Bug 26104] oleaut32/safearray shows a memory leak according to valgrind

http://bugs.winehq.org/show_bug.cgi?id=26104

Austin English  changed:

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

--- Comment #2 from Austin English  2012-09-26 14:53:59 CDT ---
Fine in wine-1.5.13-346-g0445393

[Bug 26104] oleaut32/safearray shows a memory leak according to valgrind

http://bugs.winehq.org/show_bug.cgi?id=26104

Alexandre Julliard  changed:

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

--- Comment #3 from Alexandre Julliard  2012-09-28 13:43:12 CDT ---
Closing bugs fixed in 1.5.14.