[Bug] DataGrip Metal rendering produces black rectangular artifacts on RTX 5070 Ti (2.7.2)

Open
  • Is something wrong?
#518 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
macos, rust
Domain
operating-systems

Research direction

Start by comparing DataGrip’s rendering with -Dsun.java2d.metal=true and false, using the reported RTX 5070 Ti setup and the uploaded logs as evidence. The issue does not identify a driver file or test to begin from, and it does not establish whether the Chrome observation shares a cause. Done means identifying and fixing the cause of the black rectangular artifacts, then confirming the Metal renderer works without the workaround.

Written by the indexing model from the issue text.

Description

bug
Send logs report ID

NM-B2MCVFXK, NM-TEN70EYP, NM-Q7VT870N, NM-FSQ43ZMF, NM-6FF0R4A0, NM-S9GJBTRG, NM-Y6KNXPEM, NM-1N7DV2XF, NM-KN713SFF, NM-9ZZVKM9X, NM-SJVA6QN6, NM-JX3P684P, NM-8Y7WQ389, NM-WJEF03BW, NM-NBBXZD7R, NM-9RQNAZP3

Where does it go wrong?

An app or game

What happens

Black rectangular rendering artifacts appear in DataGrip 2026.3 with the default Java2D Metal renderer enabled. The attached screenshot shows affected database-source rows, central action buttons, and the Files tree.

Image

Reproduction: start DataGrip with -Dsun.java2d.metal=true, open the default project, and display Database Explorer and Files. Changing this option to -Dsun.java2d.metal=false is the workaround used on this machine.

Hardware and software:

  • CPU: AMD Ryzen 7 9800X3D, 8 cores / 16 threads
  • RAM: 24 GiB as reported by macOS
  • GPU: NVIDIA GeForce RTX 5070 Ti, 16 GB VRAM (PCI device ID 0x2c05)
  • Platform: x86_64 Hackintosh
  • macOS: 26.7.2 (25G332)
  • 1401 and loaded NVIDIA driver components: 2.7.2
  • Monitor: G7pro Max, native 2560x1440
  • Display mode: 2048x1152 logical HiDPI, 4096x2304 framebuffer, 240 Hz (125% scaling)
  • DataGrip: 2026.3, build DB-263.7307.216
  • Installed Google Chrome: 156.0.8078.80

Related historical observation: Chrome GPU rendering flickered on older driver versions. Disabling Skia Graphite avoided flicker but fell back to software rendering. This Chrome observation has not been reproduced on 2.7.2, and a shared root cause has not been established.

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)

JetBrains DataGrip 2026.3 (DB-263.7307.216); Google Chrome 156.0.8078.80

Did you change anything yourself?

For DataGrip, the rendering comparison was -Dsun.java2d.metal=true versus false. The bundled -Dskiko.rendering.useScreenMenuBar=false setting was retained. Heap settings were left at the bundled defaults.

Diagnostic upload note: 1401 reported that driver-display.txt was not sent because the collector reached its size or file limit. It also reported that additional files were retained locally for the next Send logs attempt. The report IDs above are the successfully submitted reports shown in the upload result.

Dominant language
Rust
Stars
2.5k
Forks
233
Avg merge
3d 14h
Merged PRs (30d)
14

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nullmoth/nvidia-macos-driver

All issues in nullmoth/nvidia-macos-driver

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.