: Monday, March 20, 2006 10:34 PM
Subject: Re: [twsocket] Server problem (leaking memory)
Arno Garrels wrote:
Fastream Technologies wrote:
Ok figured out your logic. It gives the same performance/memory leak as
before. I think there is a problem with another part...
This may not be your current
: Fastream Technologies [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Wednesday, March 22, 2006 10:40 AM
Subject: Re: [twsocket] Server problem (leaking memory)
Ok here is the core of the problem: The waitforsinglemessage solution
worked
for the single thread for each
-
From: Fastream Technologies [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Wednesday, March 22, 2006 10:40 AM
Subject: Re: [twsocket] Server problem (leaking memory)
Ok here is the core of the problem: The waitforsinglemessage solution
worked
for the single
GetHeapStatus always returns 0 for all fields! Why could this be?
Regards,
SZ
- Original Message -
From: Wilfried Mestdagh [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Monday, March 20, 2006 4:39 PM
Subject: Re: [twsocket] Server problem (leaking memory)
Hello
Hello,
I don't know if it as something to do but if you use records
containing strings, always think to mystring:='' before releasing
record memory space because if you free the record, the string
allocation done inside will be kept.
regards.
--
To unsubscribe or change
: Tuesday, March 21, 2006 11:23 AM
Subject: Re: [twsocket] Server problem (leaking memory)
Hello,
I don't know if it as something to do but if you use records
containing strings, always think to mystring:='' before releasing
record memory space because if you free
0 for all fields! Why could this be?
Regards,
SZ
- Original Message -
From: Wilfried Mestdagh [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Monday, March 20, 2006 4:39 PM
Subject: Re: [twsocket] Server problem (leaking memory)
Hello,
That is a lot
Fastream Technologies wrote:
Interesting. Well I am using classes with string properties and I thought
the destructor of the AnsiString class cleans up the memory before
releasing it.
Correct, in classes you don't need to release memory allocated for strings.
But you need to finalize
Francois Piette wrote:
Fastream Technologies wrote:
Interesting. Well I am using classes with string properties and I
thought the destructor of the AnsiString class cleans up the memory
before releasing it.
Correct, in classes you don't need to release memory allocated for
strings. But you
Hello!
I saw some leaks in older Delphi versions when I didn't finalize (may be
due a mistake I made when I was a beginner?).
Seems so. Here (D3Prof) everything works properly, no leaks.
Since this time I don't really
on Delphi and free dynamic record members manually.
And you don't get
Piotr Da³ek wrote:
Hello!
I saw some leaks in older Delphi versions when I didn't finalize (may be
due a mistake I made when I was a beginner?).
Seems so. Here (D3Prof) everything works properly, no leaks.
Since this time I don't really
on Delphi and free dynamic record members
Hello!
Since this time I don't really
on Delphi and free dynamic record members manually.
And you don't get AVs and/or Invalid Pointer Operation exceptions?
No problemo.
Finalize(P^); or AString := '';
Dispose(P);
Hint: Dispose acts as Finalize+FreeMem. No need to finalize records
- Original Message -
From: Arno Garrels [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Monday, March 20, 2006 3:54 PM
Subject: Re: [twsocket] Server problem (leaking memory)
But there are various multi-threaded, TWSocketServer derived classes plus
demos in latest
- Original Message -
From: Arno Garrels [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Monday, March 20, 2006 3:54 PM
Subject: Re: [twsocket] Server problem (leaking memory)
You say that you post a message to the worker thread to let it
ThreadAttach.
What do you
Fastream Technologies wrote:
You say that you post a message to the worker thread to let it
ThreadAttach.
What do you do until the worker thread has attached?? You cannot just
post a message, you have to wait until the workerthread has allocated the
window.
What do you suggest? What should
Hello,
That is a lot leaking ;(
Use GetHeapStatus and AllocMemSize to check at regular places in your
code to find out where it starts to eat...
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
http://www.mestdagh.biz
Monday, March 20, 2006, 14:34, Fastream
Hi,
- Original Message -
From: Arno Garrels [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Monday, March 20, 2006 4:25 PM
Subject: Re: [twsocket] Server problem (leaking memory)
Fastream Technologies wrote:
You say that you post a message to the worker thread
PM
Subject: Re: [twsocket] Server problem (leaking memory)
Hi,
- Original Message -
From: Arno Garrels [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Monday, March 20, 2006 4:25 PM
Subject: Re: [twsocket] Server problem (leaking memory)
Fastream Technologies
memory)
Hi,
- Original Message -
From: Arno Garrels [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Monday, March 20, 2006 4:25 PM
Subject: Re: [twsocket] Server problem (leaking memory)
Fastream Technologies wrote:
You say that you post a message
SZ
- Original Message -
From: Fastream Technologies [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Monday, March 20, 2006 6:01 PM
Subject: Re: [twsocket] Server problem (leaking memory)
Hi,
- Original Message -
From: Arno Garrels [EMAIL PROTECTED
- Original Message -
From: Arno Garrels [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Monday, March 20, 2006 10:34 PM
Subject: Re: [twsocket] Server problem (leaking memory)
Forgot to mention that I would derive a MT TWsocketServer first that
behaves
as I like
21 matches
Mail list logo
