[Bug] Figma App Rendering Issues
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 47/100
Research direction
Start by reviewing the linked rendering capture and the supplied report IDs, then trace the Figma desktop rendering path in the Rust driver. Compare it with Figma in Chrome on macOS Sequoia and use the reports to identify the failing behavior. Done means the desktop app renders correctly and the issue is reproducible and verified as resolved.
Written by the indexing model from the issue text.
Description
Send logs report ID
NM-H4FJHC0Q, NM-KB9A7Q4F, NM-02RP48PW, NM-FSQ43ZMF, NM-RQ2B2E2S, NM-1MHSPWKF, NM-1MHSPWKF, NM-1MHSPWKF, NM-8G7DNESQ, NM-8KHVYN6F, NM-6X946RDF, NM-BTBDC9QW, NM-A5ZVEQTJ, NM-FZJ4SJJG, NM-8JW5D669, NM-WJEF03BW
Where does it go wrong?
An app or game
What happens
https://github.com/user-attachments/assets/fb13f1b0-5981-4457-9dfb-fa8e0d61514a
I am experiencing rendering glitches on the Figma desktop app. This issue does not occur on the Figma web app when using Google Chrome. I am currently running driver version 2.5.4 on macOS Sequoia.
Here are the Report IDs:
NM-H4FJHC0Q, NM-KB9A7Q4F, NM-02RP48PW, NM-FSQ43ZMF, NM-RQ2B2E2S, NM-1MHSPWKF, NM-1MHSPWKF, NM-1MHSPWKF, NM-8G7DNESQ, NM-8KHVYN6F, NM-6X946RDF, NM-BTBDC9QW, NM-A5ZVEQTJ, NM-FZJ4SJJG, NM-8JW5D669, NM-WJEF03BW
Written by you
- I wrote this report myself. AI-written issues are closed without review (see CONTRIBUTING.md).
App or game (if it is one)
Figma Desktop App V126.10.11
Did you change anything yourself?
No
- Dominant language
- Rust
- Stars
- 2.5k
- Forks
- 233
- Avg merge
- 21h 20m
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from nullmoth/nvidia-macos-driver
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nullmoth/nvidia-macos-driver#141 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
nullmoth/nvidia-macos-driver#28 ·
Maintainers usually reply within 2 days
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
nullmoth/nvidia-macos-driver#399 ·
Maintainers usually reply within 2 days
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
nullmoth/nvidia-macos-driver#396 ·
Maintainers usually reply within 2 days
-
[Bug] 画面掉帧，或者出现撕裂的情况Openbug
Difficulty 4/5 3-5 days Newbie friendliness 28/100
nullmoth/nvidia-macos-driver#393 · 2 comments ·
Maintainers usually reply within 2 days
All issues in nullmoth/nvidia-macos-driver
Similar issues
-
bug priority: P3 ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
shep-pm/shep-kelpie#1332 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
ramensoftware/windhawk#1156 · 2 comments ·
-
units: No `#` in rustdoc headingPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 67/100
rust-bitcoin/rust-bitcoin#7089 · 1 comment · 1 reaction ·
Maintainers usually reply within 2 days
-
phase:3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pchrysostomou/ananke#183 ·
Maintainers usually reply within 1 day
-
area/tools bug session-analysis
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day