# Processing 4 crashes when trying to open file

**URL:** <https://discourse.processing.org/t/processing-4-crashes-when-trying-to-open-file/34239>\
**Category:** Processing\
**Created:** [December 22, 2021, 8:57am UTC](https://discourse.processing.org/t/processing-4-crashes-when-trying-to-open-file/34239 "2021-12-22T08:57:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![MythicalSora](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/mythicalsora/32/15308_2.png) [@MythicalSora](https://discourse.processing.org/u/MythicalSora)\
**Post date:** [December 22, 2021, 8:57am UTC](https://discourse.processing.org/t/processing-4-crashes-when-trying-to-open-file/34239/1 "2021-12-22T08:57:40Z")

</div>

Hello folks! I’ve encountered a strange problem while trying to setup Processing on my machine. I managed to install and launch it, but whenever I try to open a file, it freezes for about 3 seconds and quits.

System specs:

```auto
             .',;::::;,'. michael@fedora
         .';:cccccccccccc:;,. --------------
      .;cccccccccccccccccccccc;. OS: Fedora release 35 (Thirty Five) x86_64
    .:cccccccccccccccccccccccccc:. Host: MS-7C56 1.0
  .;ccccccccccccc;.:dddl:.;ccccccc;. Kernel: 5.15.10-200.fc35.x86_64
 .:ccccccccccccc;OWMKOOXMWd;ccccccc:. Uptime: 46 mins
.:ccccccccccccc;KMMc;cc;xMMc:ccccccc:. Packages: 2662 (rpm), 10 (flatpak), 8 (snap)
,cccccccccccccc;MMM.;cc;;WW::cccccccc, Shell: zsh 5.8
:cccccccccccccc;MMM.;cccccccccccccccc: Resolution: 1920x1080, 1920x1080
:ccccccc;oxOOOo;MMM0OOk.;cccccccccccc: DE: GNOME 41.2
cccccc:0MMKxdd:;MMMkddc.;cccccccccccc; WM: Mutter
ccccc:XM0';cccc;MMM.;cccccccccccccccc' WM Theme: Mojave-dark-alt
ccccc;MMo;ccccc;MMW.;ccccccccccccccc; Theme: NewSur-dark-solid [GTK2/3]
ccccc;0MNc.ccc.xMMd:ccccccccccccccc; Icons: Numix-Circle [GTK2/3]
cccccc;dNMWXXXWM0::cccccccccccccc:, Terminal: alacritty
cccccccc;.:odl:.;cccccccccccccc:,. Terminal Font: black: "
:cccccccccccccccccccccccccccc:'. CPU: AMD Ryzen 7 3700X (16) @ 3.600GHz
.:cccccccccccccccccccccc:;,.. GPU: NVIDIA GeForce GTX 980
  '::cccccccccccccc::;,. Memory: 4477MiB / 15976MiB

```

Some more helpful details:

```auto
❯ java --version
openjdk 11.0.13 2021-10-19
OpenJDK Runtime Environment 18.9 (build 11.0.13+8)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.13+8, mixed mode, sharing)

```

```auto
Processing Location: /usr/local/share/bin
drwxrwxr-x. 1 michael michael 308 Dec 22 09:41 processing

```

I also made 2 symlinks to /usr/local/bin, which were

```auto
sudo ln -sf ${PWD}/processing /usr/local/bin
sudo ln -sf ${PWD}/processing-java /usr/local/bin

```

I also managed to get an actual error message by launching Processing through my terminal:

```auto
❯ processing

╭─ ~   ✔
╰─ WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by processing.app.platform.LinuxPlatform (file:/usr/local/share/processing/lib/pde.jar) to field sun.awt.X11.XToolkit.awtAppClassName
WARNING: Please consider reporting this to the maintainers of processing.app.platform.LinuxPlatform
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f032d42e4d8, pid=55944, tid=56146
#
# JRE version: OpenJDK Runtime Environment Temurin-11.0.12+7 (11.0.12+7) (build 11.0.12+7)
# Java VM: OpenJDK 64-Bit Server VM Temurin-11.0.12+7 (11.0.12+7, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C 0x00007f032d42e4d8
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h" (or dumping to /usr/local/share/processing/core.55944)
#
# An error report file with more information is saved as:
# /usr/local/share/processing/hs_err_pid55944.log
#
# If you would like to submit a bug report, please visit:
# https://github.com/adoptium/adoptium-support/issues
# The crash happened outside the Java Virtual Machine in native code.

```

And last but not least, my [error log](https://hastebin.nl/3mdoCDx)

Any help would be much appreciated^^