[Lewis]

Version: 2015 CI 14
Build id: 13.0.0-20150813

A fatal error will occur once “Enable Hot Reload” option is checked.

#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x5e51f759, pid=7976, tid=11864
#
# JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build 1.7.0_45-b18)
# Java VM: Java HotSpot(TM) Client VM (24.45-b08 mixed mode windows-x86 )
# Problematic frame:
# V [jvm.dll+0x26f759]
#
# 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:
# d:\MyEclipse\hs_err_pid7976.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp

[support-swapna]

Lewis,

Thank you for trying MyEclipse 2015 CI 14. Sorry that you are seeing this issue.

Can you please give us some more information to help us investigate further ? :

1. When exactly do you see this error ? Does it occur consistently?
2. Can you clarify if this error does not occur when the ‘Enable Hot Reload’ option is turned off?
3. Are you working with Tomcat or Weblogic server ? Please share the server and version details.
4. Please share with us the OS and version details. Also send us the .log file located at workspace dir/.metadata/.log.

–Swapna
MyEclipse Support

[Lewis]

Hi there, the error occurs once the ‘Enable Hot Reload’ is turned on, and it works normally after the option is turned off. The log file is not found in the directory.
Environment:
Using JRE_HOME: C:\Program Files\Java\jdk1.7.0_80
Server version: Apache Tomcat/6.0.18
Server built: Jul 22 2008 02:00:36
Server number: 6.0.18.0
OS Name: Windows 7
OS Version: 6.1
Architecture: x86
JVM Version: 1.7.0_80-b15
JVM Vendor: Oracle Corporation

[Lewis]

The issue may have something to do with this error, please see the attachment.

Attachments:

You must be logged in to view attached files.

[support-tony]

Lewis,

Thanks for the information but you haven’t mentioned when this error is occurring. Is it on deployment or when you try to run the application on the server or when changing a class file or some other time? Is the server started in normal mode or debug mode?

Regarding the .log file, there is always a .log file in the .metadata folder of the workspace directory, unless you have just cleared the log. Could you please check again? Actually, it would be best to clear the error log, then recreate the problem before sending us the .log file.

Please mention where the error message that you attached came from. Was it from the Tomcat console?

Lastly, what kind of project is causing the problem? It would help if you could attach a zip of the project, with or without source code.

[Author]

Posts