> For the complete documentation index, see [llms.txt](https://docs.diracinc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diracinc.com/support/gpu-report.md).

# GPU issue report

How to collect GPU and browser logs so Dirac can debug BuildOS 3D viewer issues.

If the BuildOS 3D viewer is blank, slow, crashes, or shows a WebGPU/GPU error, collect the reports below from the **same computer and browser** where the issue happens. These files tell Dirac which browser, operating system, graphics card, and WebGPU settings your computer is using.

## What to attach

Attach these files to your support request:

1. **Browser GPU report** from Chrome or Edge. Safari users should skip this attachment because Safari does not provide a downloadable browser GPU report.
2. **WebGPU Report** from [webgpureport.org](https://webgpureport.org/).
3. **Device information report** with your OS version, device model/specs, and graphics driver details.
4. **BuildOS console log** captured while opening the affected project.

In the message body, include the project name or link, what went wrong, and your browser name and version.

{% hint style="warning" %}
Console logs and device reports can include page URLs, project names, device serial numbers, and browser error messages. They should not include your CAD model contents, but please review the files first if your organization requires it.
{% endhint %}

## 1. Download your browser GPU report

### Chrome

1. Open a new Chrome tab.
2. Copy `chrome://gpu` and paste it into the address bar.
3. Click **Download Report to File** near the top of the page.
4. Save the file somewhere easy to find, such as your Desktop.

### Edge

1. Open a new Edge tab.
2. Copy `edge://gpu` and paste it into the address bar.
3. Click **Download Report to File** near the top of the page.
4. Save the file somewhere easy to find, such as your Desktop.

### Safari

Safari does not currently provide a `chrome://gpu`-style downloadable GPU report. If you are using Safari, skip this file and continue with the WebGPU Report and BuildOS console log below.

## 2. Download a WebGPU Report

1. In the same browser where the issue happens, go to <https://webgpureport.org/>.
2. Wait a few seconds for the report to finish loading.
3. Click the small **download** icon next to the **WebGPU Report** title at the top of the page.
4. Save the file somewhere easy to find.

## 3. Save device information

### Windows

The following will generate a DirectX Diagnostic Tool report. It includes your Windows version, computer model, processor and memory, GPU name, and GPU driver version/date.

1. Press **Windows + R**.
2. Type `dxdiag` and press **Enter**.
3. If asked whether to check if your drivers are digitally signed, click **Yes**.
4. Wait for the progress bar to finish.
5. Click **Save All Information...**.
6. Save the file somewhere easy to find.

### macOS

The following will generate a System Information report. It includes your macOS version, Mac model, processor and memory, and graphics/display information.

1. Open the **Apple menu** in the top-left corner of your screen.
2. Click **About This Mac**.
3. Click **More Info...**.
4. Scroll down and click **System Report...**.
5. In the menu bar, click **File → Save...**.
6. Save the file somewhere easy to find.

## 4. Save BuildOS logs while opening the project

These steps save the browser's Console log. The Console is a browser tool that records errors from the page.

### Chrome or Edge

For screenshots and browser-specific details, see the [Chrome DevTools Console reference](https://developer.chrome.com/docs/devtools/console/reference) or [Microsoft's browser trace guide for Edge](https://learn.microsoft.com/en-us/azure/azure-portal/capture-browser-trace).

1. Open BuildOS and sign in, and open the affected project.
2. Open the Console:
   * Windows or Linux: press **Ctrl + Shift + J**.
   * Mac: press **Option + Command + J**.
3. If you do not already see a **Console** tab, click **Console**.
4. Leave the Console open and refresh the BuildOS page.
5. Right-click anywhere in the Console message area and choose **Save as...**.
6. Save the log file somewhere easy to find.

{% hint style="info" %}
If the project is already open, open the Console first, turn on **Preserve log**, then reload the BuildOS page and reproduce the issue.
{% endhint %}

### Safari

1. If you have not used Safari developer tools before, open **Safari → Settings → Advanced** and turn on **Show features for web developers**.
2. Open BuildOS and sign in, but stop before the step that causes the issue.
3. Open **Develop → Show Web Inspector**, then click **Console**.
4. Turn on **Preserve Log** if you see that option, then clear the old messages.
5. Leave the Web Inspector open. In BuildOS, open the affected project and repeat the steps that show the problem.
6. Click inside the Console and press **Command + S** to save it.
7. If Command + S does not save a file, press **Command + A**, then **Command + C**, paste into TextEdit or another text editor, and save the file as `buildos-console-log.txt`.

## 5. Send the report to Dirac

Attach the files you saved above to your support request or email them to Dirac support.