TsiLang 7.9.5.x (7.9.6.x) + EurekaLog 12.0.x = Runtime error 216

[Stalker4]

Hi,

Delphi 11.3 Enterprise
TsiLang 7.9.5.x (7.9.6.x)
EurekaLog 12.0.x

An error occurs when closing Delphi 11.3
Runtime error 216 at 2050EFAD
and bds.exe remains hanging in the processes.

I talked with the developer of EurekaLog, he believes that the problem is in TsiLang, or more precisely in TsiLangExpert.Destroy.
Here is his answer:

Ну, смотрите - мне кажется, тут очевидна проблема:
1. RTL освобождает интерфейс, принадлежащий TsiLang.
2. К сожалению, IDE не способна показать отладочную информацию о TsiLang_11.bpl, но из предыдущего отчёта от Threads Snapshot мы знаем, что это, вероятно, вызывает TsiLangExpert.Destroy из Silangexp.pas.
3. Далее деструктор выполняет какие-то действия (TsiModuleNotifier.Unregister?), которые и приводят к ошибке.

Теперь вам нужно обратиться в техподдержку TsiLang, приложив этот скриншот (CallStack.jpg) и стек от Threads Snapshot (либо просто упоминание их функций из стека). У них есть исходный код и они должны суметь определить, в какой строке их кода происходит исключение.

[isiticov]

Hello,
Thank you for reporting. Could you please let us know if this error appears on your side all the times or there are specific steps required? Because we can't reproduce this on our side. Although we ourselves intensively use RAD 11.3 and TsiLang and never experienced such problem. Also are you sure this is not related to some other 3rd party IDE library installed?
Or did you mean (in the topic title) that having installed both TsiLang and EurekaLog always gives the error?

[Stalker4]

Hi,

An error occurs when closing Delphi 11.3
Runtime error 216 at 2050EFAD
and bds.exe remains hanging in the processes.

When EurekaLog 7.11.0.1 was installed there was no such problem.

Playback:

1. Launch Delphi 11.3.
2. Open the project from the attack.
3. Close the project.
4. Close Delphi 11.3.
And a few seconds after that we get the error "Runtime error 216".

Interesting point: If EurekaLogEvents1 is transferred from DataModule1 to Form7
and remove Unit1 with DataModule1 from the project, the error will disappear.

As I wrote above, I first talked to the EurekaLog developers about this error, and based on the contents of the call stack, it was definitely that the problem was in TsiLangExpert.

There is a picture of the call stack in my first post. And there is also a more detailed answer from the EurekaLog developers about this error.

[isiticov]

1:

When EurekaLog 7.11.0.1 was installed there was no such problem.

2:

Interesting point: If EurekaLogEvents1 is transferred from DataModule1 to Form7
and remove Unit1 with DataModule1 from the project, the error will disappear.

And I'm sure that if you remove EurekaLog from the project or the IDE, the error will disappear also.

it was definitely that the problem was in TsiLangExpert.

Anyway, we will try to install the trial version of EurekaLog and check the situation. Thank you for sending the sample project.

[isiticov]

Nice:

2023-12-26_10-42-49.png (20.61 KiB) Viewed 61573 times

[Stalker4]

And I'm sure that if you remove EurekaLog from the project or the IDE, the error will disappear also.

Yes, there is no error without EurekaLog, and there is no error with the earlier version of EurekaLog 11.0.x.
But the developer of EurekaLog, based on the tests that I did under his leadership and based on the call stack, believes that the problem is in TsiLangExpert.
As a matter of fact, I wrote his answer to you in the very first post of this topic.

Now I have TsiLang 7.9.6.0 and EurekaLog 12.0.3

Anyway, we will try to install the trial version of EurekaLog and check the situation. Thank you for sending the sample project.

I hope You can reproduce this error.

[isiticov]

Hello,
Sorry for the late reply. We've found and fixed the possible problematic code. No more run-time error 216 (at least on our side).
The fix will be available in next version release.
Thank you again for reporting this.

[Stalker4]

Hi,

Installed a new version of the library TsiLang 7.9.6.2. The error "Runtime error 216" unfortunately remained.