[NetBeans] Story when it does not start

When I try to start NetBeans as usual, it doesn't start forever with nothing coming out ... Last time it started normally ... I will write down the time when this happened here. *environment OS: Windows 10 NetBeans: Apache NetBeans IDE 11.1 Java: JDK 13

• If you edit netbeans.conf (also described at the bottom), it may not start in the same way, so if you edited netbeans.conf most recently, try restoring it first. The story when it was still useless is as follows.

Details of the error

When I try to launch it with a shortcut such as on the desktop, nothing happens. No error message is displayed. Now, try starting it at the command prompt.

C:\Program Files\NetBeans-11.1\netbeans\bin>netbeans.exe

 Again, it fails to start, but I get an error message.
 (I tried to reproduce it, but I couldn't get the error message because I couldn't. I'm sorry.)
 The error message will tell you where the log is coming from, so let's open that log. As an example of a place
 C: \ Users \ [user name] \ AppData \ Local \ Temp
 And the name of the log file is like hs_err_pid18004.log. (Since the number is the process ID, it must be a different number.) The first part of the contents looks like the following.
>\#
>\# A fatal error has been detected by the Java Runtime Environment:
>\#
>\#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007fff2a50f98a, pid=18004, tid=12052
>\#
>\# JRE version: Java(TM) SE Runtime Environment (13.0+33) (build 13+33)
>\# Java VM: Java HotSpot(TM) 64-Bit Server VM (13+33, mixed mode, sharing, tiered, >compressed oops, g1 gc, windows-amd64)
>\# Problematic frame:
>\# C  [awt.dll+0x8f98a]
>\#
>\# No core dump will be written. Minidumps are not enabled by default on client versions of >Windows
>\#
>\# If you would like to submit a bug report, please visit:
>\#   http://bugreport.java.com/bugreport/crash.jsp
>\# The crash happened outside the Java Virtual Machine in native code.
>\# See problematic frame for where to report the bug.
>#

 EXCEPTION_ACCESS_VIOLATION is the content of the error, but it is presumed that it is a memory read violation. Where the problem happened is

>\# C  [awt.dll+0x8f98a]

 It is written in the place of.
 awt.dll is a file in java \ jdk-13 \ bin. This is a file that can't be tampered with ...
# This solution
 Eventually it started successfully, but what happened was

 * JDK downgraded *

 That is. Downgrade the JDK from 13 to 12.0.2
C:\Program Files\NetBeans-11.1\netbeans\etc
 Rewrite a part of the contents of netbeans.conf in as follows. (Numbers match version)

#### **`netbeans_jdkhome="C:\Program Files\Java\jdk-12.0.2"`**

• I don't think it can be rewritten (saved) directly on Windows, so copy the file somewhere, rewrite it, and paste the rewritten file.

This succeeded in starting!

If you have a similar experience, I would appreciate it if you could refer to it.

Digression

It started successfully, so I returned netbeans.conf to try to reproduce it to write this article and for some reason it still started. What the hell was that ...