Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible memory leak on Windows CI #346

Closed
kpreid opened this issue Feb 2, 2023 · 1 comment
Closed

Possible memory leak on Windows CI #346

kpreid opened this issue Feb 2, 2023 · 1 comment
Labels
kind: bug Something isn't working as it should

Comments

@kpreid
Copy link
Owner

kpreid commented Feb 2, 2023

Recent CI runs on Windows are failing, and the timing aligns with when I updated the wgpu dependency to 0.15. The symptom is that after some number of successful render tests, they start failing like

test no_update            ... panicked: Adapter::request_device() failed: RequestDeviceError

and before I pushed a change limiting test concurrency, I also saw errors like

wgpu error: Validation Error

Caused by:
    In Queue::write_texture
    not enough memory left

which suggests that something is not being deallocated properly (by wgpu most likely, but it could also be our code) when the renderer is dropped. Investigate this and construct a repro.

@kpreid kpreid added the kind: bug Something isn't working as it should label Feb 2, 2023
@kpreid
Copy link
Owner Author

kpreid commented Mar 20, 2023

I constructed a repro and filed gfx-rs/wgpu#3498.

@kpreid kpreid closed this as completed Mar 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: bug Something isn't working as it should
Projects
None yet
Development

No branches or pull requests

1 participant