Skip to content

Eval bug: ggml-vulkan crash with vulkan 1.0 #29871

Closed

Description

@ianloic

Name and Version

I'm using ggml (from master, circa v0.25.3) in my own software.

ggml-vulcan requires Vulkan 1.2. To enforce this it calls (indirectly, via some templates) the vkEnumerateInstanceVersion function pointer from the Vulkan implementation and compares it to the constant for Vulkan 1.2.

Unfortunately, vkEnumerateInstanceVersion was only added at Vulkan 1.1 and ggml-vulkan is calling it unconditionally.

I have a CL that add a quick null check before the call. If that function is null then it's Vulkan 1.0 and we can throw an exception, like we do if vkEnumerateInstanceVersion returns Vulkan 1.1.

I encountered this on older Android devices.

Operating systems

Other? (Please let us know in description)

GGML backends

Vulkan

Hardware

Fujitsu F-01L (Android 8.1) in Firebase Test Lab

Models

n/a - this is in library/backend initialization.

Problem description & steps to reproduce

Just initializing the ggml-vulkan backend on a system with an older version of Vulkan.

First Bad Commit

No response

Relevant log output

n/a

Activity

  1. added a commit that references this issue on Oct 6, 2026
    58cb913
  2. added a commit that references this issue on Oct 8, 2026
    bd7074f
  3. added a commit that references this issue on Oct 24, 2026
    b8a839f
  4. added a commit that references this issue on Oct 28, 2026
    0d24699
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions