> ----- Original Message ----- > From: "Angus Johnson" <ajohnson@xxxxxxxxxx> > To: <delphizip@xxxxxxxxxxxxx> > Sent: Monday, March 25, 2002 8:19 AM > Subject: [delphizip] Re: Memory allocation leak in UNZDLL.DLL > > > > My understanding is that this leak is specific to Borland's C++ and Delphi > > compilers. > > > > Angus > > > > ----- Original Message ----- > > From: "Karel Rys" <delphi@xxxxxxxxx> > > ... > > > This is "very fine" ;-) Is it possible to compile the DLLs with another > > C-compiler? I made the > > > same tests with an Intel ijl15.dll and there is no memory leak. > > > I did some more searching on the newsgroup archives and found a posting by > Chris Bensen > (cbensen@xxxxxxxxxxx) date 1999/06/15 with subject Re:Bug Reporting HOW!!!: > > The real subject was this memory leak caused by LoadLibrary: > > <quote> > The default Microsoft bases adress of a .dll is 1,000,000 while the default > base address for Borland is 400,000. > If you change the base adress using rebase(an SDK tool ...) on a Borland > generated .dll it does not have the memory leak. > </quote> > > I could not test this solution because I don't have the SDK installed yet. > HTH > -- > Roger Aelbrecht > http://web.wanadoo.be/driehoeksw > Got the "rebase.exe" from a colleague and did some more tests: Tests are done on both a Win-Nt computer and on a W98 oneboth with BCB5 and TZipBuilder 1- The rebase dos not solve the memory leak, working of rebase was checked in the event log of BCB and checking the load address of ZipDll.dll 2- The Zipdll.dll as published on the website of Eric Engler produces a 200 byte memory leak 3- The same Dll rebuild on my BCB5 with condition _NO_VCL does not have the memory leak. HTH -- Roger Aelbrecht http://web.wanadoo.be/driehoeksw