Il 12/02/2017 11:39, Andi Jahja ha scritto:
> Sorry, but I did not experience memory leak in this program. This is what Mel Smith reported on comp.lang.xharbour newsgroup: > I'll investigate. In the meantime, can you compile this? > > FUNCTION MAIN() > > ? OS() > > INKEY( 0 ) > > RETURN NIL > > Do you get the same warning? > Yes, here is the warning for my ostest2.prg (as above): ************************ Memory Allocation Report Application: c:\xharbour\bin\harbour.exe xHarbour Version: xHarbour 1.2.3 Intl. (SimpLex) (Build 20170101) Compiler: Borland/Embarcadero C++ 7.2 (32-bit) Platform: Windows XP 5.1.2600 Service Pack 3 Time Occured: 2017.02.11 21:44:12 Total memory allocated: 40113 bytes (772 blocks) -------------------------------------------------------------------------------- WARNING! Memory allocated but not released: 296 bytes (1 blocks) source\common\hbfsapi.c(172) hb_fsFNameSplit() Block 1 009D40BC (size 296) "\CC\40\9D\00\00\00\00\00\00\00\00\00\DB\40\9D\00\63\3A\5C\63\67\69\5C\73\6F\75\72\63\65\5C\00\63" -------------------------------------------------------------------------------- ************************* EMG -- http://www.emagsoftware.it http://www.emagsoftware.it/emgmusic http://www.emagsoftware.it/spectrum http://www.emagsoftware.it/tbosg ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ xHarbour-developers mailing list xHarbour-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xharbour-developers
