I'm having a problem with one our projects.
The program is single-threaded and uses several forms, the TeeChart pro (v.4 - VCL) package and a fortran DLL of our own (compiled with Watcom). We are still using C++ Builder 4.
I've noticed that approx. 400 MB (yes, four hundred megabytes) of memory is allocated somewhere in my program. When I run it in the debugger, this memory is allocated even before entering winmain(). Obviously, that means none of the code we've written has been called yet and therefore cannot be responsible for this memory allocation.
This behavious has been reproduced with/without run-time DLLs, incremental linking or debugging/release parameters. It occurs on both Win98 and Win2000.
Any tips on how I can track down this memory problem ? If I can't see the responsible code in the debugger, I'm a little lost as to what I can do.
The program is single-threaded and uses several forms, the TeeChart pro (v.4 - VCL) package and a fortran DLL of our own (compiled with Watcom). We are still using C++ Builder 4.
I've noticed that approx. 400 MB (yes, four hundred megabytes) of memory is allocated somewhere in my program. When I run it in the debugger, this memory is allocated even before entering winmain(). Obviously, that means none of the code we've written has been called yet and therefore cannot be responsible for this memory allocation.
This behavious has been reproduced with/without run-time DLLs, incremental linking or debugging/release parameters. It occurs on both Win98 and Win2000.
Any tips on how I can track down this memory problem ? If I can't see the responsible code in the debugger, I'm a little lost as to what I can do.