Hi,
I'm using boundschecker to search for memory leaks. It gives a leak on this (now isolated) code fragment in a win32 app (C++, Microsoft Visual Studio 2005 pro, sp1, XP pro):
case IDC_TEST:
{
FILE* l_InputFile;
l_InputFile = _wfopen(TEXT("C:\\Test.txt
int l_Result = fclose(l_InputFile);
}
break;
There is very little going on, i press a button, a file Test.txt is opened and closed. Yet, boundschecker gives tons of warnings (after exiting the program), like:
Memory Leak, Leak exiting program
_mtinitlocknum mlock.c 279
_getstream stream.c 71
_wfsopen fopen.c 61
wfopen fopen.c 124
MainDialogProcedure winmain.cpp 112
and
Resource Leak, Kernel 32, InitializeCriticalSectionA
__crtInitCritSecAndSpinCou
__alloc_osfhnd osfinfo.c 93
tsopen_nolock open.c 385
_wsopen_helper open.c 170
_wsopen_s open.c 910
These errors all seem to originate from the _wfopen() call, when i run the program without executing this code fragment, no leaks occur.
Anyone has suggestions what the problem might be?
Kind Regards,
Daniel Dekkers
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I agree with grg99. This is a library function and is supposedly thoroughly tested.
What probably happens is that for the first call, certain allocations are done (setting up streams etc.) that will probably not occur again on subsequent calls.
Give grg99's suggestion a try, and see if more memory is "leaking" or not.
I tried the infinite loop. It doesn't seem to consume any memory. On exit, boundchecker still presents the same errors (not infinitely more ;-)). So, you are probably right about the first call allocating things. The strange thing is that if i use the same code fragment in a simple console app, with nothing else but this fragment, boundschecker accepts with no errors.
>> The strange thing is that if i use the same code fragment in a simple console app, with nothing else but this fragment, boundschecker accepts with no errors.
Might be a different way of handling file streams in a console application and a gui application. But, since there isn't a memory increase, I wouldn't worry about it ...
grg99's comment http:#19798905 answers the question, as confirmed by the asker in http:#19799325.
Business Accounts
Answer for Membership
by: grg99Posted on 2007-08-30 at 04:09:11ID: 19798905
It may be a false alarm.
Try calling this code in an infinite loop and see if the process's memory usage keeps going up.