-
Notifications
You must be signed in to change notification settings - Fork 346
buffer/device.destroy() unmaps buffer on current thread #2837
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
Conversation
Adds some language that assumes multiple threads, which we don't have, but I think it's fine. Better to have this codified now. Unfortunately the language is hand-wavy, but this isn't going to get fixed until we have a clean client-vs-shared-vs-server state split. Fixes gpuweb#2545
toji
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TIL that browser's refer to their "threads" as agents! 🧑🎓
LGTM.
|
meeting: No objection (yet) to having destroy() do unmaps. I'll remove the references to threading and leave them for later when we spec multithreading. What's important is just that we know there's a possible solution for later. |
|
I just commented it out because I don't want to lose track of proposed solutions for multithreading. |
toji
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with threading text commented out.
SHA: d71ec16 Reason: push, by @kainino0x Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
SHA: d71ec16 Reason: push, by @kainino0x Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
SHA: d71ec16 Reason: push, by @kainino0x Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* buffer/device.destroy() unmaps buffer on current thread Adds some language that assumes multiple threads, which we don't have, but I think it's fine. Better to have this codified now. Unfortunately the language is hand-wavy, but this isn't going to get fixed until we have a clean client-vs-shared-vs-server state split. Fixes gpuweb#2545 * Comment out stuff about multithreading
Adds some language that assumes multiple threads, which we don't have,but I think it's fine. Better to have this codified now.
Unfortunately the language is hand-wavy, but this isn't going to get
fixed until we have a clean client-vs-shared-vs-server state split.
Fixes #2545
Preview | Diff