Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
W
wine-winehq
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
wine
wine-winehq
Commits
4f0dfb51
Commit
4f0dfb51
authored
Dec 17, 2009
by
Vincent Povirk
Committed by
Alexandre Julliard
Dec 18, 2009
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
ole32: Fix memory leaks in the storage test.
parent
0fe54088
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
0 deletions
+5
-0
storage32.c
dlls/ole32/tests/storage32.c
+5
-0
No files found.
dlls/ole32/tests/storage32.c
View file @
4f0dfb51
...
...
@@ -877,6 +877,9 @@ static void test_streamenum(void)
ok
(
r
==
S_OK
,
"IEnumSTATSTG->Next failed
\n
"
);
ok
(
count
==
1
,
"count wrong
\n
"
);
if
(
r
==
S_OK
)
CoTaskMemFree
(
stat
.
pwcsName
);
r
=
IEnumSTATSTG_Release
(
ee
);
/* second enum... destroy the stream before reading */
...
...
@@ -1939,6 +1942,7 @@ static void test_fmtusertypestg(void)
found
=
TRUE
;
else
ok
(
0
,
"found unexpected stream or storage
\n
"
);
CoTaskMemFree
(
statstg
.
pwcsName
);
}
ok
(
found
==
TRUE
,
"expected storage to contain stream
\\
0001CompObj
\n
"
);
IEnumSTATSTG_Release
(
stat
);
...
...
@@ -1962,6 +1966,7 @@ static void test_fmtusertypestg(void)
found
=
TRUE
;
else
ok
(
0
,
"found unexpected stream or storage
\n
"
);
CoTaskMemFree
(
statstg
.
pwcsName
);
}
ok
(
found
==
TRUE
,
"expected storage to contain stream
\\
0001CompObj
\n
"
);
IEnumSTATSTG_Release
(
stat
);
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment