Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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.

Sign up for GitHub

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

Jump to bottom

How does Burn solve WGPU parent device being lost due to timeout? #1466

Closed
cryscan opened this issue Mar 13, 2024 · 0 comments
Closed

How does Burn solve WGPU parent device being lost due to timeout? #1466

cryscan opened this issue Mar 13, 2024 · 0 comments

Comments

@cryscan
Copy link

cryscan commented Mar 13, 2024

Hi! I am very interested in burn's design of its compute model, and I have a very specific question:

As far as I know, in WGPU if there are too many tasks in running or a kernel is running for too long (about 3-5 seconds?) you will panic due to "parent device being lost". How does Burn deal with this limit?
@tracel-ai tracel-ai locked and limited conversation to collaborators Mar 13, 2024
@antimora antimora converted this issue into discussion #1469 Mar 13, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cryscan