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
6d6c3e5d
Commit
6d6c3e5d
authored
Jul 30, 2013
by
Piotr Caban
Committed by
Alexandre Julliard
Jul 30, 2013
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
oleaut32: Don't leak BSTRs allocated in string_list and name_list.
parent
4133fb43
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
0 deletions
+2
-0
typelib.c
dlls/oleaut32/typelib.c
+2
-0
No files found.
dlls/oleaut32/typelib.c
View file @
6d6c3e5d
...
@@ -4594,11 +4594,13 @@ static ULONG WINAPI ITypeLib2_fnRelease( ITypeLib2 *iface)
...
@@ -4594,11 +4594,13 @@ static ULONG WINAPI ITypeLib2_fnRelease( ITypeLib2 *iface)
LIST_FOR_EACH_ENTRY_SAFE
(
tlbstr
,
tlbstr_next
,
&
This
->
string_list
,
TLBString
,
entry
)
{
LIST_FOR_EACH_ENTRY_SAFE
(
tlbstr
,
tlbstr_next
,
&
This
->
string_list
,
TLBString
,
entry
)
{
list_remove
(
&
tlbstr
->
entry
);
list_remove
(
&
tlbstr
->
entry
);
SysFreeString
(
tlbstr
->
str
);
heap_free
(
tlbstr
);
heap_free
(
tlbstr
);
}
}
LIST_FOR_EACH_ENTRY_SAFE
(
tlbstr
,
tlbstr_next
,
&
This
->
name_list
,
TLBString
,
entry
)
{
LIST_FOR_EACH_ENTRY_SAFE
(
tlbstr
,
tlbstr_next
,
&
This
->
name_list
,
TLBString
,
entry
)
{
list_remove
(
&
tlbstr
->
entry
);
list_remove
(
&
tlbstr
->
entry
);
SysFreeString
(
tlbstr
->
str
);
heap_free
(
tlbstr
);
heap_free
(
tlbstr
);
}
}
...
...
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