Develop Reference

how can i solve java fatal error during jframe [duplicate]

This question already has answers here:
Eclipse EXCEPTION_ACCESS_VIOLATION crash
(2 answers)
Closed 3 years ago.
I'm using JFrame (window builder) with eclipse.
When I go to design tab and click components or something. Sometimes eclipse just closes without throwing any error and when I open eclipse again my Jframe file is vanished in air.
I can't use the name of my Jframe file again.
'Type with same name but different case exists.' occurs.
I found out that every time it happens new file such as hs_err_pd13544 is created . So I copied part of it.
I tried reinstalling java and eclipse several times without any help.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffdecbcaca8, pid=13544, tid=29532
#
# JRE version: Java(TM) SE Runtime Environment (13.0.1+9) (build 13.0.1+9)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (13.0.1+9, mixed mode, sharing, tiered, compressed oops, g1 gc, windows-amd64)
# Problematic frame:
# C [MSCTF.dll+0x2aca8]
#
# 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.
#
--------------- S U M M A R Y ------------
Command Line: -Dosgi.requiredJavaVersion=1.8 -Dosgi.instance.area.default=#user.home/eclipse-workspace -XX:+UseG1GC -XX:+UseStringDeduplication --add-modules=ALL-SYSTEM -Dosgi.requiredJavaVersion=1.8 -Dosgi.dataAreaRequiresExplicitInit=true -Xms256m -Xmx1024m --add-modules=ALL-SYSTEM -Declipse.p2.max.threads=10 -Doomph.update.url=http://download.eclipse.org/oomph/updates/milestone/latest -Doomph.redirection.index.redirection=index:/->http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/ -Dosgi.requiredJavaVersion=1.8 -Dosgi.instance.area.default=#user.home/eclipse-workspace -XX:+UseG1GC -XX:+UseStringDeduplication --add-modules=ALL-SYSTEM -Dosgi.requiredJavaVersion=1.8 -Dosgi.dataAreaRequiresExplicitInit=true -Xms256m -Xmx1024m --add-modules=ALL-SYSTEM -Declipse.p2.max.threads=10 -Doomph.update.url=http://download.eclipse.org/oomph/updates/milestone/latest -Doomph.redirection.index.redirection=index:/->http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/
Host: Intel(R) Core(TM) i5-8265U CPU # 1.60GHz, 8 cores, 7G, Windows 10 , 64 bit Build 18362 (10.0.18362.329)
Time: Thu Nov 21 13:46:57 2019 ´eCN¹I±¹ C￥AؽA elapsed time: 77 seconds (0d 0h 1m 17s)

1)
I'm using JFrame (window builder) with eclipse.
--> For Swing frame work, Netbeans IDE is more feasible or best option due to lighter and faster than eclipse.Try the same code with Netbeans IDE.
2) Another way is..
Use New/latest version of Eclipse Or update existing eclipse.

Unexpected JVM terminated. Exit code=13 Error while starting STS 3.9?

Problem
I was able to start STS yesterday but unexpected error is coming today.
JVM terminated. Exit code=13
/home/jalaj/Java/Java8/jre1.8.0_144/bin/java
-Dosgi.requiredJavaVersion=1.8
-Xms40m
-Dosgi.module.lock.timeout=10
-Xverify:none
-Xmx1200m
-jar /home/jalaj/Downloads/sts-bundle/sts-3.9.0.RELEASE//plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
-os linux
-ws gtk
-arch x86_64
-showsplash
-launcher /home/jalaj/Downloads/sts-bundle/sts-3.9.0.RELEASE/STS
-name STS
--launcher.library /home/jalaj/Downloads/sts-bundle/sts-3.9.0.RELEASE//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.500.v20170531-1133/eclipse_1624.so
-startup /home/jalaj/Downloads/sts-bundle/sts-3.9.0.RELEASE//plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
--launcher.overrideVmargs
-exitdata 378017
-product org.springsource.sts.ide
-vm /home/jalaj/Java/Java8/jre1.8.0_144/bin/java
-vmargs
-Dosgi.requiredJavaVersion=1.8
-Xms40m
-Dosgi.module.lock.timeout=10
-Xverify:none
-Xmx1200m
-jar /home/jalaj/Downloads/sts-bundle/sts-3.9.0.RELEASE//plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
My Analysis
1)I have checked my system JAVA_HOME and JRE_HOME path,javac and java version and have made changes in STS.ini after it failed to start but still I am not getting any result.
echo $JAVA_HOME
/home/jalaj/Java/Java8/jdk1.8.0_144
echo $JRE_HOME
/home/jalaj/Java/Java8/jre1.8.0_144
jalaj#jalaj-X540YA:~$ javac -version
javac 1.8.0_144
jalaj#jalaj-X540YA:~$ java -version
java version "1.8.0_144"
Java(TM) SE Runtime Environment (build 1.8.0_144-b01)
Java HotSpot(TM) Server VM (build 25.144-b01, mixed mode)
My STS.ini file
-startup
plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
--launcher.library plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.500.v20170531-1133
-product
org.springsource.sts.ide
--launcher.defaultAction
openFile
-vm
/home/jalaj/Java/Java8/jre1.8.0_144/bin
-vmargs
-Dosgi.requiredJavaVersion=1.8
-Xms40m
-Dosgi.module.lock.timeout=10
-Xverify:none
-Xmx1200m
Can anyone guide me how to resolve this issue.I have researched various threads about this error but couldn't find any solution.

It looks like your JAVA_HOME points to a 32bit JDK installation whereas the STS installation that you are trying to run is a 64bit installation. Make sure you have a 64bit JDK installed and configured.
In addition to that I also vaguely remember that you have the -vm option in the ini file as the first one in that file. But I am not sure if that is really related to the problem.

Cannot run carrot2 workbench 3.10.2 in Kubuntu 14.04

I have Java 1.7.0...
$ java -version
java version "1.7.0_75"
Java(TM) SE Runtime Environment (build 1.7.0_75-b13)
Java HotSpot(TM) Server VM (build 24.75-b04, mixed mode)
And Ubuntu 14.04.2 LTS, running KDE (Kubuntu). When I run ./carrot2-workbench-ubuntu I get...
Java HotSpot(TM) Server VM warning: You have loaded library /var/downloads/a/packages/carrot2-workbench-3.10.2/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20140603-1326/eclipse_1605.so which might have disabled stack guard. The VM will try to fix the stack guard now.
It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.
2015-08-03 20:01:08,984 INFO org.carrot2.workbench.core.WorkbenchCorePlugin: Changed instanceLocation to: file:/var/downloads/a/packages/carrot2-workbench-3.10.2/workspace/
2015-08-03 20:01:09,223 INFO org.carrot2.util.xslt.TemplatesPool: XSLT transformer factory: com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
After that I get a pop-up window that says the following:
JVM terminated. Exit code=13
/usr/lib/jvm/jdk1.7.0/bin/java
-Xms256m
-Xmx512m
-Dorg.eclipse.update.reconcile=false
-Dlog4j.configuration=log4j-workbench.xml
-jar /var/downloads/a/packages/carrot2-workbench-3.10.2/plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar
-os linux
-ws gtk
-arch x86_64
-showsplash
-launcher /var/downloads/a/packages/carrot2-workbench-3.10.2/carrot2-workbench
-name Carrot2-workbench
--launcher.library /var/downloads/a/packages/carrot2-workbench-3.10.2/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20140603-1326/eclipse_1605.so
-startup /var/downloads/a/packages/carrot2-workbench-3.10.2/plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar
--launcher.overrideVmargs
-exitdata 1af001e
-data #noDefault
-vm /usr/lib/jvm/jdk1.7.0/bin/java
-vmargs
-Xms256m
-Xmx512m
-Dorg.eclipse.update.reconcile=false
-Dlog4j.configuration=log4j-workbench.xml
-jar /var/downloads/a/packages/carrot2-workbench-3.10.2/plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar
Can someone please help me decipher what's wrong? Thanks.

Thanks for reporting the issue (although the mailing list would be more convenient). I'll look into this.
http://issues.carrot2.org/browse/CARROT-1108

Version 1.5.0_30 of the JVM is not suitable for this product. 1.6 or greater is required OSX

I recently downloaded eclipse for RCP and RAP developers. I am running OSX 10.5.8, and when I tried running eclipse i got the error "Version 1.5.0_30 of the JVM is not suitable for this product. 1.6 or greater is required". I went to utilities then java preferences and made sure that Java SE 6 was at the top of the preferred order list, it was not so I moved it up. I verified my system was pointing to the correct version
user-Macbook-Pro:~ user$ java -version
java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03-384-9M3425)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02-384, mixed mode)
however i still get the same error when trying to open eclipse. Any suggestions? Thank you for the help

It starts working after I modified eclipse.ini like below and added
-vm C:\Program Files\Java\jdk1.7.0_45\bin\javaw.exe
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
-launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20120913-144807
-product
com.android.ide.eclipse.adt.package.product
-showsplash
com.android.ide.eclipse.adt.package.product
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vm
C:\Program Files\Java\jdk1.7.0_45\bin\javaw.exe
-vmargs
-Dosgi.requiredJavaVersion=1.6
-Xms40m
-Xmx768m
-Declipse.buildId=v22.3.0-887826
-XX:MaxPermSize=512M

Out of memory error in eclipse.why?

When i create a new project in "Eclipse" IDE.Suddenly it shows an alert message "Out of memory error".I cannot identify the reason.
If any one know the reason please tell me.

Try to start eclipse with follow paramenters:
eclipse.exe -vmargs -Xms512m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=128m
Or justify these parameters for your requirements

Go to your Eclipse setup folder
If you are running Eclipse on Mac OS X then
Right click on eclipse.app icon
Click on Show Package Contents
Open eclipse.ini file
Change below parameters
-Xms512m
-Xmx3000m (Hoping your developer box has >4GB of memory)
Add below parameters
-XX:PermSize=256m
-XX:MaxPermSize=512m

The most obvious explanation is that you are truly out of memory. In which case starting Eclipse with a bigger heap should help
-vmargs -Xmx256M
varying the 256M to see what works for you.
I would not expect to see this problem if you have just a few simple projects. If you are using additional plugins then conceivably the amount of heap you need may need to be increased.

Not sure if relevant to your problem, but I just had a similar problem with a Swing project using OpenJDK 7.
After several cycles of starting (the Run button) and closing ('X' / Alt+F4) my application, I got this error in the console:
Exception in thread "main" java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:691)
at sun.awt.AWTAutoShutdown.activateBlockerThread(AWTAutoShutdown.java:334)
at sun.awt.AWTAutoShutdown.notifyPeerMapUpdated(AWTAutoShutdown.java:215)
at sun.awt.AWTAutoShutdown.registerPeer(AWTAutoShutdown.java:348)
at sun.awt.SunToolkit.targetCreatedPeer(SunToolkit.java:313)
at sun.awt.X11.XToolkit.createFrame(XToolkit.java:410)
at java.awt.Frame.addNotify(Frame.java:477)
at java.awt.Window.show(Window.java:1031)
at java.awt.Component.show(Component.java:1651)
at java.awt.Component.setVisible(Component.java:1603)
at java.awt.Window.setVisible(Window.java:1014)
at tool.BAT.main(BAT.java:11)
And sometimes, I got another sort of error:
Error occurred during initialization of VM
java.lang.OutOfMemoryError: unable to create new native thread
and then, if I tried to run it once more, Java crashed:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x0000000000000000, pid=30388, tid=139776854689536
#
# JRE version: 7.0_07-b30
# Java VM: OpenJDK 64-Bit Server VM (23.2-b09 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C 0x0000000000000000
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/mcmlxxxvi/workspace/bat/hs_err_pid30388.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# http://icedtea.classpath.org/bugzilla
#
top revealed the cause of the problem (notice virtual memory usage):
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
30619 mcmlxxxv 20 0 3271m 390m 45m S 2.0 13.0 0:38.88 java
30667 mcmlxxxv 20 0 2172m 35m 12m S 0.3 1.2 0:01.00 java
30688 mcmlxxxv 20 0 2172m 35m 12m S 0.3 1.2 0:00.96 java
30710 mcmlxxxv 20 0 2172m 35m 12m S 0.0 1.2 0:00.97 java
These were all instances of my application, which had not been closed. Still not sure why so much virtual memory was allocated per instance - probably there's some option for that. (I have 3GiB of physical memory, by the way).
Here's my main() method:
public static void main(String[] args) {
JFrame frame = new JFrame();
//frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
frame.setSize(400, 300);
frame.setVisible(true);
}
I saw the commented line in a tutorial and specifically disabled it to see what would happen. What happened was that that it defaulted to HIDE_ON_CLOSE, which did not close and dispose of the frame.
Setting setDefaultCloseOperation to EXIT_ON_CLOSE was the solution for me. Interested to see input from more knowledgeable people on this, though.

Open Your eclipse.ini file
XXMaxPermSize will be 256m.
Change the value to 512m.
Restart your eclipse.
Now you will not see any memory issues in Eclipse.
In Brief See below:
Before
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
256M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
After:
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
512M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
512m

For everyone (like me) who ends up at the bottom without fixing it...
My Eclipse ran out of memeory every time I tried to save a specific file.
Eclipse has a bug where it is unable to handle formatting a comment between a method type and a method name, like the code given below. The fix is to move the comment up or down
public String
// Never put a comment here, Eclipse will run out of memory
getName() {
return "name";
}

You have to use setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
You can see from here