https://bugs.winehq.org/show_bug.cgi?id=36127
Bug ID: 36127 Summary: valgrind shows a leak in oleaut32/tests/safearray.c Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: oleaut32 Assignee: wine-bugs@winehq.org Reporter: austinenglish@gmail.com
../../../tools/runtest -q -P wine -T ../../.. -M oleaut32.dll -p oleaut32_test.exe.so safearray && touch safearray.ok preloader: Warning: failed to reserve range 00110000-68000000 preloader: Warning: failed to reserve range 7f000000-82000000 ==24053== 40 bytes in 1 blocks are definitely lost in loss record 93 of 267 ==24053== at 0x7BC4C735: notify_alloc (heap.c:255) ==24053== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==24053== by 0x4FE9FD7: SAFEARRAY_Malloc (safearray.c:103) ==24053== by 0x4FEAEEC: SafeArrayAllocData (safearray.c:569) ==24053== by 0x4FEA3EA: SAFEARRAY_Create (safearray.c:244) ==24053== by 0x4FEB083: SafeArrayCreate (safearray.c:609) ==24053== by 0x4C65027: test_safearray (safearray.c:680) ==24053== by 0x4C6BB6E: func_safearray (safearray.c:2073) ==24053== by 0x4D75F00: run_test (test.h:584) ==24053== by 0x4D762EF: main (test.h:654) ==24053==
https://bugs.winehq.org/show_bug.cgi?id=36127
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Assignee|wine-bugs@winehq.org |bunglehead@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=36127
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Assignee|bunglehead@gmail.com |wine-bugs@winehq.org
https://bugs.winehq.org/show_bug.cgi?id=36127
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |valgrind
https://bugs.winehq.org/show_bug.cgi?id=36127
--- Comment #1 from Nikolay Sivov bunglehead@gmail.com --- This looks intentional, test destroys descriptor without destroying data first, and that's the point of this test. Can we suppress this by comment message for example?
https://bugs.winehq.org/show_bug.cgi?id=36127
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX
--- Comment #2 from Austin English austinenglish@gmail.com --- (In reply to Nikolay Sivov from comment #1)
This looks intentional, test destroys descriptor without destroying data first, and that's the point of this test. Can we suppress this by comment message for example?
No, in valgrind they're separate and done in suppression files. But yes, I can suppress it.
https://bugs.winehq.org/show_bug.cgi?id=36127
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from Austin English austinenglish@gmail.com --- Closing.