Yes the events get destroyed in the threads destructor. I verified they
were being freed up.
It would usually happen when lots of connect disconnects happened in a
Once that error 161 popped it could not be recovered from, all new
connections would fail on the teventobject.create.
It would also happen much sooner when compiled as 32bit.
I guess as long a using the GUID works long term it shouldn't be an issue.
"Do you destroy the event again once it's no longer used? Of course if you
require the events the whole time it might indeed be a Windows limitation.
fpc-pascal maillist - firstname.lastname@example.org