-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory leaks in DispatchEvents.cpp. #43
Comments
EJP286CRSKW
changed the title
Memory leask in DispatchEvents.cpp.
Memory leaks in DispatchEvents.cpp.
Oct 3, 2023
So they become BSTR typeLib = NULL;
if (_typelib != NULL)
{
// why is this UTF instead of unicode? Then we could probably drop the A2W
const char *typelib = env->GetStringUTFChars(_typelib, NULL);
typeLib = A2W(typelib);
env->ReleaseStringUTFChars(_typelib, typelib);
// printf("we have a type lib %ls\n",typeLib);
}
// find progid if any
LPOLESTR bsProgId = NULL;
if (_progid != NULL)
{
// why is this UTF instead of unicode? Then we could probably drop the A2W
const char *progid = env->GetStringUTFChars(_progid, NULL);
bsProgId = A2W(progid);
env->ReleaseStringUTFChars(_progid, progid)
// printf("we have an applicaton %ls\n",bsProgId);
} |
freemansoft
added a commit
that referenced
this issue
Mar 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are several
GetStringUTFChars()
calls in this file that are followed by comments asking whether this result needs to be released, byReleaseStringUTFChars()
.The answer is yes, they do need to be released.
The text was updated successfully, but these errors were encountered: