Skip to content

Vulkan OOM logic can prevent creating large buffers #9206

@andyleiserson

Description

@andyleiserson

Test case for this is webgpu:api,validation,buffer,create:limit:* on Radeon Pro W7600.

It appears that because there are two heaps and candidate allocations are checked against both of them, allocations larger than the host-visible heap will always be rejected.

// NOTE: We might end up checking multiple heaps since gpu-alloc doesn't have a way

(It is also possible to exhaust the host-visible heap by running the CTS test webgpu:api,operation,adapter,requestAdapter:*, but in that case I think it could really be exhausted by rapid creation of many devices.)

The topic of large buffers is also discussed in #8105.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: ctsIssues stemming from the WebGPU Conformance Test Suitebackend: vulkanIssues with Vulkanplatform: linuxLinux Specific Issuestype: bugSomething isn't working

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions