DLL Server hangs when TDAConnectionManager is destroyed

Data Abstract
1

Hi,
Using Delphi 10 Seattle 32-bit with RO/DA 9.0.97.1245.
When closing the app using DLL server, it hangs at TDAConnectionManager.Destroy on line fTimer.Free.
I can trace it to procedure TROThreadTimer.Free and see that it goes to the line WaitFor indefinitely.
Any idea why this happens ?
Thanks.

2

WaitFor won’t work correctly from DLL_PROCESS_DETACH so I can suggest to stop timer in ConnectionManager like:

ConnectionManager.ClearPool;
ConnectionManager.PoolTimeoutSeconds := 0;

after this, you can free ConnectionManager.

3

Unfortunately, this doesn’t solve the problem which now occurs on the line: ConnectionManager.PoolTimeoutSeconds := 0
fTimer.Free is called in procedure TDAConnectionManager.SetPoolTimeoutSeconds which then goes back to WaitFor.
Any other ideas ?
Thanks.

4

you can don’t use thread polling at all.
set these properties in design-time or after creating ConnectionManager.

ConnectionManager.PoolingEnabled := False;
ConnectionManager.PoolTimeoutSeconds := 0;

in this case, internal TROThreadTimer won’t be created.

5

Problem fixed for connection manager but now occurs in destructor TROInMemorySessionManager.Destroy => KillTimer
Why ?
It looks like something is going wrong with timers

6

I can’t reproduce this issue with simple testcase.
can you create a simple testcase that reproduces this case, pls?

7

It will be very hard to extract from the whole app. I’ll see what I can do.
Meanwhile, any idea what could cause this behavior with timers ?
Thanks.

8

destroying of threads inside DLL - this is a reason for such problems.
you can try to test this workaround:
copy implementation of TROThread.WaitFor to TROThreadTimer.WaitFor. it may solve your issue.

9

Yes, copy implementation of TROThread.WaitFor to TROThreadTimer.WaitFor fixed the problem!
Will it be included in a next update ?

10

Thanks, logged as bugs://75520

11

bugs://75520 got closed with status fixed.

12

yes, it will be in the next beta

15

WOW! When this patch will be available?

Many thank’s!

16

Hi,

#75520 was fixed 4 years ago

edit: you can ignore all messages with ixxxxx issues. it isn’t related to actual issues

1 Like
17

Revisiting this problem many years later as it occurs exactly the same after updating to 10.0.0.1607.
And TROThreadTimer doesn’t have a WaitFor method anymore.
Any help will be greatly appreciated.

18

Hi,

Can you create a simple testcase for this case, pls?
I’ll retest it with your testcase

you can drop email to support@ for keeping privacy

19

The problem is exactly the same as the one described earlier. I can’t extract from a very complex project. If you have an initial EXE ↔ DLL sample project, please send it and I’ll change it until I can reproduce this problem. Thanks

20

Hi,

try to replace

destructor TDAConnectionManager.Destroy;
..
  FreeAndNil(fTimer);

with

destructor TDAConnectionManager.Destroy;
..
  fTimer.Free; fTimer := nil;

looks like we did some refactoring and replaced fTimer.Free; fTimer := nil; with FreeAndNil(fTimer); again :frowning:

UPDATE: fixed for .1611

21

I confirm that both:

  • FTimer.AsyncFree;
  • fTimer.Free; fTimer := nil;

Fix the problem. Thank you.