Jump to content
Lajos Juhász

F2084 Internal Error: D33566

Recommended Posts

Is it just me or D11.1 update 1 has a problem debugging a runtime package?

 

I was changing/debugging the core runtime package for the application. The workflow was the folowing:

 

1.) compile the package,

2.) run the package inside a host application.

3.) Make change

4.) Restart the IDE.

 

Without step 4 I would get instantly internal error.

Share this post


Link to post

For what platform ?

 

From my setup here:

Under Android64, debugging is broken in more complex projects, already since >= 10.4 or so, simply starts veeery slow, shows blackscreen and stops.

Under Android32, debugging is still fine and fluid.

 

But I haven't seen such D33566 yet.

My recommendationm for any Internal error is, to completely clean all compiled, temporary stuff, and build the project new.

That resolved the internal errors in 99.9% in my cases, which leads to my opinion that internal errors are causes mostly by mainy failing processes, leaving DCU or other files in a ghost state.

 

Share this post


Link to post
Posted (edited)
1 hour ago, Rollo62 said:

That resolved the internal errors in 99.9% in my cases, which leads to my opinion that internal errors are causes mostly by mainy failing processes, leaving DCU or other files in a ghost state.

Unfortunately that doesn't help for a VCL bpl. I have another common internal error:

 

[dcc32 Fatal Error] core.dpk(358): F2084 Internal Error: AV11A8360D(11A60000)-R00FC101E-0

 

For this it was enough to add a period after the unit name:

unit csv.;

 

Try Compile the package (compilation failed as it should be), remove the period and when I tried to compile it I got this error. Of course I cannot reproduce this with a "hello world package".

 

Edited by Lajos Juhász

Share this post


Link to post
7 minutes ago, Lajos Juhász said:

remove the period and when I tried to compile it I got this error.

If that happens consistently, then you might be able to trace the last unit compiled using sysinternals process monitor. Having that might help you work backwards into a "reproduce failure package".  You would have to judge if that activity is worth the effort, and i honestly do not know if it will fix anything for you.

 

I always disable Enable Unit Directory Cache under Computer\HKEY_CURRENT_USER\SOFTWARE\Embarcadero\BDS\22.0\Compiling

Share this post


Link to post

Now I get the same error while trying to debug Synedit 2. Just change something in source for SynEditDR.dproj to trigger compile as Break point stopped working and got an internal error.

Share this post


Link to post

I have exactly the same problem than  Lajos Juhász in Alexandria 11.1. I did only use the RadServer template.  So it is not something to do with my code or large project. As soon as I change something (I change a comment), then  I get the internal error.  I did apply 11.1 Update 1 patch but it does not fix the issue. I did also install the patch for people working in Windows 11 (I am working in Windows 10) but it does not help.

Note that there is a Defect (RSP-37631) entered in https://quality.embarcadero.com/ 

I do suspect that it has to do with Visual Studio installed on the same machine (I have Visual Studio 2019). I have seen this in the quality portal for related defect.

Could you (@Lajos Juhász ) tell us If you have Visual Studio installed?

image.thumb.png.b449dd935b2fc18e85cc521819a44e2d.png

Share this post


Link to post
6 hours ago, Alexandre Jacquot said:

Could you (@Lajos Juhász ) tell us If you have Visual Studio installed?

Of course I don't have. I am a Delphi developer.

Share this post


Link to post

I did made this investigation and report it to embarcadero QA portal: Install windows 10 in a VM, install delphi 11.1. Create a RadServer project from template. Result : I am running into the same issue. So it is 100% in the hand of embarcadero. 

 

Share this post


Link to post

IMHO it is always the same of this:  https://en.delphipraxis.net/topic/4628-several-f2084-internal-error-on-delphi-1042/

It's not a D11.1 problem. This kind of problems (f2084 internal errors, av in dc32xxx.dll, ecc )  were introduced (or emphasized) at least in D10.4 if not in previuos versions.

I'm now using 11.1 too and fighting with these issues every days. There are several reports on QC but they never solved the problem. 

 

In my case these problems increase exponentially working on a big project group containing several BPLs, DLLs and EXEs (all VCL), when I compile one of the BPLs that are used (statically or dynamically) by the other projects. In these scenario the crash is almost at every compile. Closing the IDE and restarting all works fine.

 

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×