microsoft / microsoft/DirectXShaderCompiler
Stackoverflow Crash on Firefox/Chrome with a HTML WebGPU fuzzing testcase that generates a long shader/ multiple assignments. Crash occurs in DXC.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 3.7k
- Forks
- 900
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 44
Description
Open attached HTML file in release Firefox or release Chrome.
Enter 5000 in the input-box.
Click Run.
Actual: Both browsers will crash.
Expected: Not so
Originally reported in Firefox bugzilla here: https://bugzilla.mozilla.org/show_bug.cgi?id=1965507
The analyssi there suggests that this is specific to DXC.
Tetcase generated to stress-test the WebGPU implementation of browsers. Testcase geenrated using chatgpt, but idea and prompt are mine.
You can experiment with the number of loopcpunts in the input-box. For eamply, you can enter an absurd number like 500000 and see what it does.
Contributor guide
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
Open the attached webgpu_shader_fuzz.HTML in a release Firefox or Chrome build, enter 5000, and click Run to reproduce the crash. Then read the linked Firefox bug 1965507 and investigate the DXC path implicated there. Done means the testcase no longer crashes either browser.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100