Recurring Crash A4D on Client

[Darin Schroeder]

Aparajita,

We just upgraded to v20R3 (100.285). The 4D Server is running on Windows Server 2016.

A4D (v7.2)  is running as a client on a separate Windows Server 2016 box. It's the only application on it.

Since upgrading, we have had multiple crashes where only the A4D client is affected. We get an 'Unexpectedly Quit' dialog. It starts up again with no issues. Sometimes it will run for a few hours, sometimes it will crash 30-60 minutes later. I'm not sure if it's load necessarily because it's crashed very early in the morning with light traffic.

I'm unable to find a pattern to what may be running when it crashes. I'm trying to figure out what the best course of action would be.

When we were having issues with another client on another DB, we had installed Procdump to get some details about the crash. Would that provide any useful information in this case?

While Procdump is running, Many of these type of exceptions are listed in the terminal window:

[19:56:10] Exception: E06D7363.?AW4EExecuteState@Interpreter@a4d@plugin@@

Thanks,

Darin

[Aparajita]

My apologies for not posting about this sooner.

DO NOT ATTEMPT TO RUN ACTIVE4D ON V20!!!

Unfortunately it seems there is a bug in the 4D plugin API — most likely a double free of memory — which is causing these crashes. My client has established definitively that it is a v20 bug, because the same DB does not crash on v19.

This has already been reported to 4D, but please send them your procdumps and I encourage everyone here to put pressure on them to fix it, as this is a complete blocker. In the meantime if there is any way to downgrade to v19, I recommend it.

[Darin Schroeder]

We had been running this in our staging area for months without issue. There must be something distinct happening to trigger the crash that we didn't encounter in staging.

Unfortunately, going back to v19 isn't really possible at this time. I'll have to determine if there is a specific event causing it and in the meantime, report it to 4D as you advised.

Thanks Aparajita.

Darin

[Darin Schroeder]

Aparajita,

Is 4D 19.7 LTS ok to use?

Darin

[Aparajita]

Any version prior to v20.

[jwill...@gmail.com]

So do we know if this has been resolved yet.  I've seen some discussions on discuss.4d.com but it's not clear to me if this is fixed or not.

[Darin Schroeder]

Not sure ... We ended up going to v19 R8.100252.

[Aparajita]

As far as I know it has not been fixed. 4D wants us to run the app in debug mode, which makes it so slow it is unusable. So we are kind of stuck.