We Keep Coding

EXCEPTION_ACCESS_VIOLATION when uploading code to STM32

I'm getting the following error when trying to upload code to a STM32 "Bluepill" board using the STM32duino Bootloader aka DFU method:
maple_loader v0.1
Resetting to bootloader via DTR pulse
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000007110b5db, pid=1720, tid=0x0000000000000c98
#
# JRE version: Java(TM) SE Runtime Environment (8.0_261-b12) (build 1.8.0_261-b12)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.261-b12 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [jSSC-2.8_x86_64.dll+0xb5db]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
This doesn't happen in another one of my computers. What's happening?

Found a strange fix.
Had to change the path to the Java binary to point to the provided version inside Arduino installation folder.
This is done through Environment Variables in Windows Control panel. You may also need to uninstall any other Java versions if you have any.

I had this same issue as well and I fixed it by uninstalling both the 32-bit and 64-bit versions of Java and reinstalling only the 64-bit version.
I have not tested whether installing the 32-bit version again will cause the issue.

Can not start Glassfish server

When I attempt to run my java web application project on Netbeans 8.02, I keep getting this error:
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007fff49cf42ec, pid=2768, tid=0x0000000000002860
#
# JRE version: Java(TM) SE Runtime Environment (8.0_111-b14) (build 1.8.0_111-b14)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.111-b14 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [chtbrkg.dll+0x242ec]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\ZOOM IT\Downloads\Compressed\java_ee_sdk-7u2\glassfish4\glassfish\domains\domain1\config\hs_err_pid2768.log
#
# 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.
# Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=192m; support was removed in 8.0
and this dialog box a bit later.
I am using windows 10.
java version "1.8.0_111"
Java(TM) SE Runtime Environment (build 1.8.0_111-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.111-b14, mixed mode)
Cannot start GlassFish 4.1 from within Netbeans 8.0.1 Service area This problem relates to occupied port,which certainly is not my case.

This is not a problem with GlassFish. Java has failed due to a problem with this dll file: chtbrkg.dll. Looking around on the Internet, there is a hint from a Minecraft forum that this is likely related to some kind of 3rd party software and there are quite a few pages which associate that DLL with malware.
Remove the DLL and try again.

It does look like some virus chtbrkg.dll here is the details - greatis.com/blog/how-to/remove-uninstall-chtbrkg-dll-virus.h‌​tm
The issue has been verified here Eclipse Mars 2 jvm crash
Same has been reported on https://bugs.openjdk.java.net and closed as not an issue, here is the link https://bugs.openjdk.java.net/browse/JDK-8171850
Please uninstall virus from above mentioned approach and try.

Failed to write core dump. Minidumps are not enabled by default on client versions of Windows in IntelliJ

I get an error when I open a project in IntelliJ. It only happens with one Project. I am not even able to modify the code. When I open the project in IntelliJ it instantly shows me an utf-8 file with the error message.
I reinstalled IntelliJ
I tried changing the directory of the project
I tried reinstalling Java
I get this Error message:
A fatal error has been detected by the Java Runtime Environment
EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000022b3302,
pid=5876, tid=7496 JRE version: Java(TM) SE Runtime Environment
(8.0_91-b14) (build 1.8.0_91-b14)Java VM: Java HotSpot(TM) 64-Bit
Server VM (25.91-b14 mixed mode windows-amd64 compressed oops)
Problematic frame: V [jvm.dll+0x113302] Failed to write core dump.
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

File-> invalidate cache and restart option work for me , for this issue.

Eclipse PHP SIGSEGV When Opening Project File

Eclipse is crashing every time when I attempt to open a newly created project file and I've done everything I can think of. This only happened after updating my system (Manjaro) and now even reinstalling eclipse and deleting all the files, I can find pertenent to eclipse it is still doing it.
It is very frustrating and I can't really work until this issue is fixed. Thanks in advance. I'm trying to open the files via the PHP Explorer View as well as the Navigator view (built into eclipse).
Eclipse Version: 4.6.1.
Java Version:
openjdk version "1.8.0_112"
OpenJDK Runtime Environment (build 1.8.0_112-b15)
OpenJDK 64-Bit Server VM (build 25.112-b15, mixed mode)
I've tried to revert eclipse back to the previous 4.6.0 but the issue still persists.
Here is the start of the crash log:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f04a8da6cc6, pid=26036, tid=0x00007f054f909700
#
# JRE version: OpenJDK Runtime Environment (8.0_112-b15) (build 1.8.0_112-b15)
# Java VM: OpenJDK 64-Bit Server VM (25.112-b15 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libgtk-3.so.0+0x173cc6]
#
# Core dump written. Default location: /home/taylor/core or core.26036
#
# 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.
#
The rest of the log is very long, and I can link it if needed but the character limit is not beg enough.

Sorry, this is not an answer, is a comment but I've not enough reputation to make it.
I have the same problem with Eclipse Neon 4.6 JEE, Java VM: Java HotSpot(TM) 64-Bit Server VM 1.8.0_112, Manjaro recently updated and libgtk-3.so.0+0x173cc6 library.
To avoid being stopped you can try, temporaly, to run Eclipse with GTK2:
Verify you have gtk2 installed
Edit eclipse.ini and add:
--launcher.GTK_version
2

Switching from 32-bit to 64 bit causes exit for a leap motion listener on java

After taking a java program (with Eclipse IDE) to use leap motion listener from a 32-bit windows to a 64-bit windows, the program appears to be running properly.
The problem is that now the connection to the controller is initialized, connected then immediately exits without me doing anything.
I tried putting my hand over the controller and got this error
A fatal error has been detected by the Java Runtime Environment:
EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000007fee8b4a975, pid=10516, >tid=23920
JRE version: Java(TM) SE Runtime Environment (8.0_51-b16) (build 1.8.0_51->b16)
Java VM: Java HotSpot(TM) 64-Bit Server VM (25.51-b03 mixed mode windows->amd64 compressed oops)
Problematic frame:
C [Leap.dll+0x2a975]
Failed to write core dump. Minidumps are not enabled by default on client >versions of Windows
An error report file with more information is saved as:
M:\Leapduino\Leapduino_test\hs_err_pid10516.log
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.
I tried to change to an older version of java, but no luck either.
Any ideas how it can be fixed ?

I received an answer from Joe_Ward from Team Leap Motion:
https://community.leapmotion.com/t/leap-crash-java-windows/703?u=sgerish