#1486 8.3.2 leaks

obsolete: 8.3.2
closed-invalid
nobody
5
2001-04-17
2001-04-17
No

I rebuilt tcl8.3.2 from sources and with
-DTCL_MEM_DEBUG. Then I ran the test:

makrel:dawson-350> ./tclsh8.3
% info tclversion
8.3
% memory info
total mallocs 4591
total frees 2545
current packets allocated 2046
current bytes allocated 182677
maximum packets allocated 2067
maximum bytes allocated 186819

% memory info
total mallocs 4640
total frees 2588
current packets allocated 2052
current bytes allocated 182936
maximum packets allocated 2067
maximum bytes allocated 186819

%

It is "intutively obvious" that the packets/bytes
allocated should not change between the two commands.

Is there something non-intuitive going on, or is there
a bug somewhere?

Discussion

  • Jeffrey Hobbs

    Jeffrey Hobbs - 2001-04-17

    Logged In: YES
    user_id=72656

    It is intuitively obvious - remember that just running
    commands in the Tcl shell does make use of the history
    mechanism (to support !<event> and ^abc^def style shell
    command syntaxes). If the first thing you do is [proc
    history {args} {}], then you'll get more what you expect.

    BTW, 8.3.2 does have a mem leak in channels. Get 8.3.3.

     
  • Jeffrey Hobbs

    Jeffrey Hobbs - 2001-04-17
    • status: open --> closed-invalid
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks