Frequently Asked Questions

JRE crashes on Windows and gives an access violation error while running Red5 Pro

QUESTION:

I have setup Red5 Pro on Windows as per site instructions. However, the server won’t start due to JRE crashes with an access violation error pointing to a problematic frame in cauldron dll. How can I get around this?

#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ff80cf0c86e, pid=6892, tid=0x0000000000001b8c
#
# 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 [red5pro-cauldron-7.2.0.dll+0x4c86e]
#
# Core dump written. Default location: C:\red5proserver\hs_err_pid6892.mdmp
#
# 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.
#

ANSWER:

Some versions of Red5 Pro have been known to experience this issue on Windows systems (including server editions) with the latest or newer JDK/JRE installations.

To resolve this issue, you need to uninstall the current version of JDK/JRE that is crashing and rollback to Java SE Development Kit 8u191. It can be obtained from the oracle java archives site.