Hello,

A friend from Brazil found a small problem in "resolve" unit.

Before execute the test:

http://imagebin.org/256886

After execute the test:

http://imagebin.org/256887

And the test is:

procedure TForm1.Button1Click(Sender : TObject);
begin
  with TInetSocket.Create('www.google.com', 80) do
  try
  finally
    Free;
  end;
end;

After debug the TInetSocket class, the problem continues in:

procedure TForm1.Button1Click(Sender : TObject);
begin
 with THostResolver.Create(nil) do
  try
    if not NameLookup('www.google.com') then
      raise Exception.Create('não resolvido');
  finally
    Free;
  end;
end;

And finally, you can reproduce it with:

uses
  resolve, winsock;
procedure TForm1.Button1Click(Sender: TObject);
var
  FHostEntry: PHostEnt;
begin
  FHostEntry := gethostbyname('www.google.com.br');
end;

But, if in code above I undeclare the "resolve" unit, I got only one thread (threads = 1).

Is this a bug?

Thank you!

Oops,

2013/5/8 silvioprog

... gethostbyname('www.google.com') ...

The resolver or netdb units do not create threads by themselves.

But the windows Winsock routines may create threads (I would expect this), and these may show up in your process manager.

Michael.

2013/5/8 Michael Van Canneyt

But my project will always have a thread that is never released? Even when I freed my objects, that thread is still there.

Well, if this is done by the Windows API, I think we have nothing to do hehe...

Maybe it use the thread again, try many requests if there is more threads?

2013/5/8 Zaher Dirkey

Maybe it use the thread again, try many requests if there is more threads?

It keep only one thread. :)

Sorry Michael, Zaher and friends. A friend tested it in Delphi on Window XP and it's same to Free Pascal.