VisualD having many bugs since upgrading

[Aphexus]

Recently I upgraded Visual Studio 2022 to latest(I didn't upgrade for several months) and upgraded VisualD too (everything to latest).

Ever since I've been having major issues.

1. I cannot debug programs. Either VS crashes or I get an error about "evaluating expression 0" which stalls everything and VS just consumes an infinite amount of memory. Happens in x64 and x86 even with the most basic project. I'm not sure if it's trying to evaluate a watch or local variable and is stalling out or what.

Literally this is the program causing the problem:

import std.stdio;

int main() { return 0; }

with a BP on the return. The crash only happens when the BP exists.

2. VS sometimes just crashes when opening a project. This seems to be related to intellisense as it also crashes when I try to use intellisense. Intellisense is broken completely as it never returns anything. Well, maybe sometimes it works but I don't use it any more because of the crashing.

3. I get this error: Error errors in imported modules: Error: C:\D\dmd\src\phobos\std\range\package.d(1028): => shortened method not enabled, compile with compiler switch -preview=shortenedMethods...

I've added those to the command line in options but it does nothing. I do not get that error in x86 just x64. I lied, it is now happening in x86. [I changed to mago debugger and it started happening but not sure if it's actually connected]

VisualD has become unusable because of these. I had no problems with it before. All I can do is write code and execute it outside VS and use console printing to try and debug.

VisualStudio.17.Release/17.7.5+34202.233 Microsoft .NET Framework Version 4.8.09032

Visual D 1.3.1 Integration of the D Programming Language into Visual Studio

I just updated to Visual D 1.4 beta and same issue as 1. With the update and setting to x64:

cannot launch debugger on C:\Temp\test.exe hr = 89710016

This is mago related(because I had it set to it before) so changing to mixed mode works. Of course setting BP causes error.

This was a new project so all the settings should be the default project settings.

I'm not really sure what is going on or how to provide any more useful information. Again, everything was working fine until I updated VS.

I also constantly get this "Microsoft Visual C++ runtime library" error dialog that says:

Program C:\Program Files (x86)\visualD\dmdserver.exe

HEAP CORRUPTION DETECTED: after Normal Block (#xxxxx) at xxxxxx. CRT detected that the application wrote to memory after end of heap buffer.

It constantly pops up once it gets going(may be related to intellisense)