# Processing error with display attached to MacBook

**URL:** <https://discourse.processing.org/t/processing-error-with-display-attached-to-macbook/38216>\
**Category:** Processing\
**Created:** [August 3, 2022, 7:39pm UTC](https://discourse.processing.org/t/processing-error-with-display-attached-to-macbook/38216 "2022-08-03T19:39:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![steve\_j](https://avatars.discourse-cdn.com/v4/letter/s/4491bb/32.png) [@steve\_j](https://discourse.processing.org/u/steve_j)\
**Post date:** [August 3, 2022, 7:39pm UTC](https://discourse.processing.org/t/processing-error-with-display-attached-to-macbook/38216/1 "2022-08-03T19:39:43Z")

</div>

Processing has stopped working when i have a high res monitor attached to my M1 macbook.

This only occurs when using a USB C out, HDMI works fine at 3840 x 2160  
Running USB C out to a 3840 x 2160 display works fine also  
The USB C is outputting and i get the following error when attached to a 3840 x 2400 display

It was running fine, then just started throwing the following error. If anyone can shed some light on what might be happening?

# 

# A fatal error has been detected by the Java Runtime Environment:

# 

# SIGILL (0x4) at pc=0x00007ff808cb77ba, pid=3172, tid=7939

# 

# JRE version: OpenJDK Runtime Environment Temurin-17.0.2+8 (17.0.2+8) (build 17.0.2+8)

# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.2+8 (17.0.2+8, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, bsd-amd64)

# Problematic frame:

# C [CoreFoundation+0x1b77ba] CFEqual.cold.1+0xe

# 

# No core dump will be written. Core dumps have been disabled. To enable core dumping, try “ulimit -c unlimited” before starting Java again

# 

# An error report file with more information is saved as:

# /var/folders/pw/1jx099px43s19mk1d0fq31hr0000gn/T//hs\_err\_pid3172.log

# 

# If you would like to submit a bug report, please visit:

# [GitHub · Where software is built](https://github.com/adoptium/adoptium-support/issues)

# The crash happened outside the Java Virtual Machine in native code.

# See problematic frame for where to report the bug.

# 

Could not run the sketch (Target VM failed to initialize).  
For more information, read Help → Troubleshooting.

---

<div class="post-metadata">

**Author:** ![th75](https://avatars.discourse-cdn.com/v4/letter/t/ebca7d/32.png) [@th75](https://discourse.processing.org/u/th75)\
**Post date:** [August 4, 2022, 12:32pm UTC](https://discourse.processing.org/t/processing-error-with-display-attached-to-macbook/38216/2 "2022-08-04T12:32:18Z")

</div>

hi,  
sorry, no solution here but does it fail if the display is attached before launching processing? had this issue few times, but i think only when connected/disconnected while processing is working

---

<div class="post-metadata">

**Author:** ![steve\_j](https://avatars.discourse-cdn.com/v4/letter/s/4491bb/32.png) [@steve\_j](https://discourse.processing.org/u/steve_j)\
**Post date:** [August 4, 2022, 12:46pm UTC](https://discourse.processing.org/t/processing-error-with-display-attached-to-macbook/38216/3 "2022-08-04T12:46:45Z")

</div>

Fails if the display is attached before launching processing or running the sketch, runs fine if attaching the display after the sketch is running.

Strangely the issue doesn’t occur if i dont declare P2D or P3D, so it will run P2D if not declared, but in this case i need P3D.

Have tried both the arm and 64bit intel versions, havent tried processing 3 yet.

---

<div class="post-metadata">

**Author:** ![steve\_j](https://avatars.discourse-cdn.com/v4/letter/s/4491bb/32.png) [@steve\_j](https://discourse.processing.org/u/steve_j)\
**Post date:** [August 5, 2022, 11:51am UTC](https://discourse.processing.org/t/processing-error-with-display-attached-to-macbook/38216/4 "2022-08-05T11:51:36Z")

</div>

Ok, little update on this. The issue seems to be when the display resolution is not in a 16:9 or 4:3 format. So any 16:10 (ie wuxga) or custom ratios wont run if declaring P2D or P3D

Is anyone on a PC or intel mac able to reproduce this?

Also happening on the intel P3 release.

EDIT: got a hold of a WUXGA monitor that it works fine on. Seems datapath might be the culprit. Gonna step back for a bit. If anyone else has any thoughts please share.