[Bug]: device: "cpu" should not be affected by GPU dependencies

[devunion]

🐛 Bug Description

The original problem was described here: #1755.

SDK was configured to use CPU:

        modelConfig: {
            device: "cpu",
            ctx_size: 1024,
        },

So, I assume that any problems with GPU drivers should not cause any problems if we use CPU mode.

🔄 Steps to Reproduce

1. Ensure that you've obsolete Vulcan drivers (for ex, 1.2.3).
2. Init SDK

    modelId = await loadModel({
        modelSrc: LLAMA_3_2_1B_INST_Q4_0,
        modelType: "llm",
        modelConfig: {
            device: "cpu",
            ctx_size: 1024,
        },
        onProgress: (progress) => {
            console.log(progress);
        },
    });

✅ Expected Behavior

SDK should work even with obsolete GPU drivers

❌ Actual Behavior

SDK fails with the exteption

📜 Stack Trace / Error Output

вќЊ Error: Error: The specified procedure could not be found.

    at Addon.load (bare:/bare.js:3488:32)
    at require.addon (bare:/bare.bundle/node_modules/bare-module/index.js:778:30)
    at file:///C:/work/vitya/my_progs/___SantaBrowser/qvac-sdk/qvac-examples/node_modules/@qvac/llm-llamacpp/binding.js:1:26
    at Module._evaluate (bare:/bare.bundle/node_modules/bare-module/index.js:210:7)
    at Module._transform (bare:/bare.bundle/node_modules/bare-module/index.js:122:12)
    at Module.load (bare:/bare.bundle/node_modules/bare-module/index.js:467:21)
    at require (bare:/bare.bundle/node_modules/bare-module/index.js:763:25)
    at file:///C:/work/vitya/my_progs/___SantaBrowser/qvac-sdk/qvac-examples/node_modules/@qvac/llm-llamacpp/addonLogging.js:1:17
    at Module._evaluate (bare:/bare.bundle/node_modules/bare-module/index.js:210:7)
    at Module._onevaluate (bare:/bare.bundle/node_modules/bare-module/index.js:291:12)
Uncaught ReferenceError: process is not defined
    at file:///C:/work/vitya/my_progs/___SantaBrowser/qvac-sdk/qvac-examples/quickstart.js:29:5

💻 Platform / OS

Windows (x64)

🖥️ OS Version

10

⚙️ Runtime Environment

Node.js

📦 Runtime Version

22.22

🏷️ SDK Version

0.9.1

📋 Relevant Dependencies

"dependencies": {
    "@qvac/sdk": "^0.9.1"
  },

🔁 Frequency

Always (100%)

🔥 Severity

Critical - Complete blocker, no workaround

🩹 Workaround

No response

📎 Additional Context

No response

✅ Checklist

• I have searched existing issues for duplicates
• I have included a minimal reproduction
• I am using a supported SDK version

[victorchimakanu]

You are right that this should not happen. If device: 'cpu' is set, the SDK should not touch GPU dependencies at any point. The failure you are seeing is a real gap in how the addon is loaded.

One thing worth trying first: you are on SDK 0.9.1 and the current version is 0.12.0. Could you update to 0.12.0 and let me know if the CPU mode failure persists? If it does, that gives the team a clean repro on a current version to work from.

The process is not defined error is a separate issue. It appears in the quickstart example and points to a Bare runtime and Node.js mismatch in that specific file, not in the SDK itself.

I am flagging the underlying issue of CPU mode loading GPU dependencies to the team regardless of the version, as it is a valid bug report.

[victorchimakanu]

One correction on my earlier reply: the latest SDK version is 0.13.5, not 0.12.0. Could you retest with @qvac/sdk@0.13.5 and let us know if CPU mode still loads GPU dependencies?

[victorchimakanu]

Update from the team: the CPU/GPU isolation issue is confirmed as a known bug on the platform side. It is being tracked internally. Will update this thread when a fix lands.

[viktar-l]

@victorchimakanu I've update my GPU drivers and can't reproduce this problem anymore. But it is still actual for those users who has obsolete drivers.

[victorchimakanu]

Thanks for confirming. The underlying issue , CPU mode loading GPU dependencies when device: "cpu" is set — is still a real bug regardless of driver version and is being tracked by the team.

[victorchimakanu]

Progress update. Dynamic backend loading has landed for desktop Linux in the @qvac/llm-llamacpp addon as of v0.28.0 (2026-06-22, #2733). The Vulkan GPU backend and the CPU micro-architecture variants now load as separate modules on demand, instead of the library hard-linking Vulkan at load time. On Linux that means device: "cpu" no longer pulls in the Vulkan dependency at load.

Windows is not covered by this yet and is still in progress. Updating to a current @qvac/sdk release pulls in the newer addon. If you are on Linux and still see CPU mode loading GPU dependencies after updating, reply with your @qvac/sdk and @qvac/llm-llamacpp versions and we will take another look.