Error when compiling vst3

[David Healey]

@pcs800 Which commit of HISE are you using? Which version of Visual Studio?

[Sifres]

@pcs800 said in Error when compiling vst3:

include_hi_scripting_01.obj : fatal error LNK1000: Internal error during BuildLibrary.EmitMember [H:\Common\HISE Projec
ts\Whineykid\Binaries\Builds\VisualStudio2022\WhinyKid Wah Pedal_SharedCode.vcxproj]
Press any key to continue . . .

ChatGPT pro seems to be convinced that its a storage issue. Are you running this from a network drive perhaps?

[pcs800]

@Sifres Yes I am running from a networked drive. I always have.
I'll go check to see if the drive is getting full

[pcs800]

@Sifres There's 119GB free on that drive

[David Healey]

@pcs800 How much space on the C drive?

[pcs800]

@David-Healey Of the server or the dev pc?
Dev pc 614GB
Server 1.7TB

[pcs800]

@David-Healey Claude says:
That's a linker crash, not a code error. The key line is:

ExceptionCode = C0000006

That's STATUS_IN_PAGE_ERROR — the linker (link.exe) tried to read a page of memory that couldn't be loaded from disk. It's crashing inside the linker itself, not failing due to bad code. The LNK1000: Internal error during BuildLibrary.EmitMember confirms this — it's an internal linker fault, not something wrong with your HISE script or C++.

The most likely causes in order of probability:

Disk/file issue — The project is on H:\, which looks like a network drive or secondary drive. If that drive had a hiccup during the link stage (slow response, brief disconnect, full cache), you'd get exactly this. C00000C4 in the exception info points to a file mapping fault.

Low disk space or RAM — The linker is mapping large object files into memory. If you're tight on either, it can fail this way.

Corrupted intermediate files — The x64\Release\Shared Code\ intermediates may have gotten into a bad state. That MSB8028 warning about shared intermediates between projects is a red flag for this.

What to try:

1. Do a full clean of the build (delete the Binaries\Builds\VisualStudio2022\ folder entirely, or use HISE's clean option), then rebuild fresh.
2. If H:\ is a network or external drive, try moving the project to a local C:\ path and compiling from there.
3. Check available disk space on H:\ and on C:\ (where temp files land).
4. Try compiling again immediately — sometimes it's a one-time I/O glitch and it just works on retry.

The fact that it repeated the crash dump ~25+ times in a loop before hitting LNK1000 suggests the linker kept retrying internally and hitting the same bad page each time, which further points to a storage/I/O issue rather than anything wrong with your actual plugin code.

[David Healey]

@pcs800 said in Error when compiling vst3:

Of the server or the dev pc?

Whichever system has Visual Studio on it.

[pcs800]

@David-Healey That would be the dev pc, lots of space.

[pcs800]

@David-Healey I copied one of the projects to the local C drive and compiled the vst3 without error.
I am perplexed as to why this is suddenly happening. I have been running projects from my file server since I started using hise, with no issue.
I guess I will put in a new drive in case there's something wrong with the current one.

[pcs800]

@pcs800 And strangely enough, today I can compile to the network drive again without issue.
The server must have been low on bluetooth fluid