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

Spontanious validation error #26

Open
Poly2it opened this issue Nov 13, 2024 · 6 comments
Open

Spontanious validation error #26

Poly2it opened this issue Nov 13, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@Poly2it
Copy link

Poly2it commented Nov 13, 2024

After running for some time, this program may run into fatal errors. The rest of my system was running in a faultless state the whole time.

thread 'main' panicked at /home/bach/.cargo/git/checkouts/wgpu-f9afa33caa1e84c9/ffb4852/wgpu/src/backend/wgpu_core.rs:23
Error in Queue::submit: Validation Error

Caused by:
  Parent device is lost

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
@ArthurBrussee
Copy link
Owner

Unfortunately that error is basically what happens if anything goes wrong, so it's reallly hard to say :/

What platforms is this on? Is this during training or rendering? How many steps had you run? Did it work ok before that?

@Poly2it
Copy link
Author

Poly2it commented Nov 13, 2024

Unfortunately that error is basically what happens if anything goes wrong, so it's reallly hard to say :/

What platforms is this on? Is this during training or rendering? How many steps had you run? Did it work ok before that?

During training, on Linux. In my experience it is independent of previous iterations, and seems not to be an issue of a lack of system resources. Maybe there should be some printouts?

@ArthurBrussee ArthurBrussee added the bug Something isn't working label Nov 16, 2024
@ArthurBrussee
Copy link
Owner

Does this by any chance happen at the same time as #28 ?

@Poly2it
Copy link
Author

Poly2it commented Nov 22, 2024

Does this by any chance happen at the same time as #28 ?

No, this leaves a trace, #28 is a hard termination.

@ArthurBrussee
Copy link
Owner

Hiya, I'm wondering if this still happens after some recent stability updates. I have a suspicion of what was causing it which is fixed now.

@Poly2it
Copy link
Author

Poly2it commented Dec 10, 2024

Hiya, I'm wondering if this still happens after some recent stability updates. I have a suspicion of what was causing it which is fixed now.

I have not experienced it as of recently. I could see if I can recreate it before/after the fix commit if you'd like to link it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants