BabylonJS/Babylon.js · critical · Error

Unable to create vertex buffer

Error message

Unable to create vertex buffer

What it means

Thrown by the private _createVertexBuffer when gl.createBuffer() returns null, meaning the WebGL driver could not allocate a new buffer object for vertex data. This is a GPU/driver resource allocation failure, not a data problem.

Source

Thrown at packages/dev/core/src/Engines/thinEngine.pure.ts:1316

        this._cachedVertexBuffers = null;
    }

    /**
     * Creates a vertex buffer
     * @param data the data or size for the vertex buffer
     * @param _updatable whether the buffer should be created as updatable
     * @param _label defines the label of the buffer (for debug purpose)
     * @returns the new WebGL static buffer
     */
    public createVertexBuffer(data: DataArray | number, _updatable?: boolean, _label?: string): DataBuffer {
        return this._createVertexBuffer(data, this._gl.STATIC_DRAW);
    }

    private _createVertexBuffer(data: DataArray | number, usage: number): DataBuffer {
        const vbo = this._gl.createBuffer();

        if (!vbo) {
            throw new Error("Unable to create vertex buffer");
        }

        const dataBuffer = new WebGLDataBuffer(vbo);
        this.bindArrayBuffer(dataBuffer);

        if (typeof data !== "number") {
            if (data instanceof Array) {
                this._gl.bufferData(this._gl.ARRAY_BUFFER, new Float32Array(data), usage);
                dataBuffer.capacity = data.length * 4;
            } else {
                this._gl.bufferData(this._gl.ARRAY_BUFFER, <ArrayBuffer>data, usage);
                dataBuffer.capacity = data.byteLength;
            }
        } else {
            this._gl.bufferData(this._gl.ARRAY_BUFFER, new Uint8Array(data), usage);
            dataBuffer.capacity = data;
        }

View on GitHub (pinned to 0592b347b8)

Solutions

1. Check gl.isContextLost(); if lost, handle context restoration (recreate engine/scene)
2. Reduce vertex data memory: dispose unused meshes/buffers, use smaller vertex formats (e.g. Float32 -> Int16 where possible)
3. Retry buffer creation after freeing GPU resources (engine.disposeUnusedTextures / disposing meshes)
4. Monitor memory during development with engine.getGlInfo and browser GPU diagnostics

Example fix

// before
const vb = new VertexBuffer(engine, hugeFloat32Array, 'position'); // OOM on low-VRAM GPUs
// after
mesh.geometry.releaseVertexBuffer('position'); // free old buffers before allocating
const vb = new VertexBuffer(engine, downgradedData, 'position');

function canAllocateBuffer(gl: WebGLRenderingContext): boolean {
  return !gl.isContextLost() && gl.getError() === gl.NO_ERROR;
}

null

try {
  const buffer = engine.createVertexBuffer(data);
} catch (e) {
  if ((e as Error).message === 'Unable to create vertex buffer') {
    disposeHeavyAssets(); // free GPU memory then retry
  } else throw e;
}

When it happens

Trigger: gl.createBuffer() returning null due to exhausted GPU memory, a lost WebGL context, or exceeding the driver's buffer-object limit when creating vertex buffers via createVertexBuffer / updateVertexBuffer pathways.

Common situations: Large scenes exhausting GPU memory (many meshes, high-poly geometry); running on integrated GPUs with little VRAM; creating buffers after context loss; leaking buffers by never disposing old geometry in dynamic streaming scenarios.

Related errors

• Unable to create index buffer
• Unable to create multi sampled framebuffer
• Unable to create instance buffer
• Atmosphere is not supported on WebGL ${engine.version}.
• Instanced arrays are required for MSDF text rendering.

AI-assisted analysis of BabylonJS/Babylon.js@0592b347b8 (2026-08-30). Data as JSON: /api/errors/b8e4ac95ea71c3a0. Report an issue: GitHub.