wcandillon / wcandillon/react-native-webgpu
bug: The `device.lost` promise is not being resolved when the device gets destroyed
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 70
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 23
Description
In my experiments, calling device.destroy() on a device doesn't cause the device.lost promise to be resolved, while it does so in the browser. This would allow better mechanisms for recovering from device loss.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the React Native WebGPU implementation of device.destroy() and the device.lost promise, then compare its behavior with the browser behavior described in the issue. Reproduce destruction and observe whether device.lost resolves; the work is done when the promise resolves consistently after device destruction and a regression test covers it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- computer-graphics, mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100