TidSimpleServer Error while writing stream

[jamie]

I installed Indy 10 from the OPM, all seems to work ok except for TIDSimpleServer when dropped on the form I get an error message that it had
an error while writing. etc.

Same is true when removing it from the form.

This component is on the "Indy Servers -Core" tab when installed.

Thank you to who it may concern

Jamie

[LeP]

Even though @Remy frequents this forum, it would be better to post the problem here:
https://github.com/IndySockets/Indy/issues

[Remy Lebeau]

for TIDSimpleServer when dropped on the form I get an error message that it had an error while writing. etc.

Same is true when removing it from the form.

TIdSimpleServer doesn't "write" anything when created or destroyed, especially at design-time. What is the EXACT error message, verbatim? This does not sound like an Indy error message or a socket error message. I'm guessing it's an IDE error message during DFM/LFM management.

[jamie]

Yes it is related to writing the LFM file.
This is using the 64bit ide. I dont know abt the 32bit.

 But in both cases adding and removing, the same av message.

It happed in 4.2 where i initally installed indy and the upgrade to 4.6 of Lazarus.

So i take it there could be a pulbished property or custum non-publish data that is having issues.

Ill try to post an image later.
Jamie.

[Remy Lebeau]

Yes it is related to writing the LFM file.
This is using the 64bit ide. I dont know abt the 32bit.

 But in both cases adding and removing, the same av message.

Please provide the EXACT error message.

It happed in 4.2 where i initally installed indy and the upgrade to 4.6 of Lazarus.

So i take it there could be a pulbished property or custum non-publish data that is having issues.

Possibly. I need more details to diagnose it.

[jamie]

Excuse the off color, something went wrong but here it is.

[Remy Lebeau]

Do you have the same Access Violation error if you create the TIdSimpleServer in code instead of in the Form Designer?

[jamie]

Ok, I've done some more testing.

as a reminder, this is being done in the 64-Windows version of Lazarus 4.6

I can dynamically create that component and it does not create an AV.

However, I put "HeapTrc" in play and I get memory leaks when exiting the Test app.

Also I just discovered a more bazar error and that is, if you use HeapTrc and simply do no more than include the "LazIndy" as a dependency without using any of the components, build the blank app, run and then exit, HeapTrc reports leaks!

 Remove that dependency and no leaks.

 It's strange that somehow just putting that dependency in there causes Head-Trace leak reports when no components are dropped on the form?


Jamie

[jamie]

More info:

 I looked in the Indy package requirements and saw the IDEIntF as a requirement.

 That package causes HeapTrc Memory leaks just having it in the Require Package list.

Maybe I should report this because the Indy also requires this.

I can't say if that is what's causing the problem with the TIDSimpleServer however.

Jamie

[paweld]

However, I put "HeapTrc" in play and I get memory leaks when exiting the Test app.

Also I just discovered a more bazar error and that is, if you use HeapTrc and simply do no more than include the "LazIndy" as a dependency without using any of the components, build the blank app, run and then exit, HeapTrc reports leaks!

 Remove that dependency and no leaks.

 It's strange that somehow just putting that dependency in there causes Head-Trace leak reports when no components are dropped on the form?

You must define FREE_ON_FINAL in the IdCompilerDefines.inc file: https://forum.lazarus.freepascal.org/index.php/topic,39257.msg428027.html#msg428027

Code: Pascal  [Select][+][-]

1. // $DEFINE the following if the global objects in the IdStack and IdThread
2. // units should be freed on finalization
3. {$DEFINE FREE_ON_FINAL}
4. {.$UNDEF FREE_ON_FINAL}

[jamie]

Interesting I will need to reinstall Indy on that PC and the others and try your change I understand the need as to way it was setup thar way but a class variable counter may solve that in the final section to free all. Ect.

 In any case currently there seems to be other issues brewing in the 64 bit ide that could be causing issues and appears to be tabcontrol related with a more than normal amounts of tabs allocated.

Ill pickup on this later, i need to resolve some Irradiation issues today on a 2 Mev unit. I know a small one. 
Jamie