Community
Participate
Working Groups
Build Identifier: 20100917-0705 Created an archive file from eclipse galileo workspace that is 5.2GB in size. Selecting the file and starting the import in eclipse helio, it immediately crashed. I suggest that this is a major bug because it prevents upgrading from galileo to helio via the projects export and import feature. The following was the output in the console: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f6af40f3f31, pid=19307, tid=140097354241808 # # JRE version: 6.0_22-b04 # Java VM: Java HotSpot(TM) 64-Bit Server VM (17.1-b03 mixed mode linux-amd64 ) # Problematic frame: # C [libzip.so+0xaf31] # # An error report file with more information is saved as: # /mydir/eclipse/helios/hs_err_pid19307.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # I will add the /mydir/eclipse/helios/hs_err_pid19307.log as an attachment. Reproducible: Always Steps to Reproduce: 1.export projects to archive in galileo 2.import projects from archive in helio 3.
Created attachment 182270 [details] error output log file
Did you try by increasing the memory in the vm params? Also I don't understand the usecase. Why do you have to export from Galileo and import from Helios? You can simply use the Helios version on the same workspace. Even if you have to use different workspaces, why can't you simply use the "Existing projects into workspace" import wizard and point the wizard to the Galileo workspace? Even if you have to do an export and import,why are you using File System import wizard? Shouldn't you be using Existing projects into workspace wizard for that?
The following is the contents of my eclipse.ini: -startup plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar --launcher.library plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.1.R36x_v20100810 -product org.eclipse.epp.package.jee.product --launcher.defaultAction openFile -showsplash org.eclipse.platform --launcher.XXMaxPermSize 512m --launcher.defaultAction openFile -vmargs -Dosgi.requiredJavaVersion=1.5 -XX:PermSize=512m -XX:MaxPermSize=512m -Xms1024m -Xmx4096m -XX:-UseGCOverheadLimit In terms of the use case, my needs were as follows: 1) Retain the current galileo workspace given that jboss tools for helios are still in beta - so that I can easily go back to galileo if moving to helios turns out to effectively be too early for my requirements at this time. 2) Periodically export workspace to zip for backup purposes 3) Check that I am able to successfully add the plugins that I need to helios: JBoss Tools, ZeroTurnaround's JRebel, logviewer, and Virtual Word Wrap. 4) Export or copy the current galileo workspace for import into the workspace for helios. Export/import via zip crashed prompting me to submit this error. Copying the projects from the galileo workspace to the helios workspace and using "Existing projects into workspace" import wizard worked fine. Thus, I suggest that this remain a bug (generally an application crashing without any user friendly pop-up message or other is a bug) but perhaps the severity should be reduced to Normal or I suppose even minor though I would recommend at least Normal given the crash. Regards, Jeff
Forgot to mention, given the question on memory. My system specs are as follows: HP TouchSmart tx2 laptop (We run our servers on these laptops as well.) CPU: AMD Turion X2 64-bit (dual cpu's) 8GB memory Ubuntu 10.04LTS 64-bit 500GB SATA HDD with roughly 100GB free disk space
(In reply to comment #3) > -vmargs > -XX:PermSize=512m > -XX:MaxPermSize=512m > -Xms1024m > -Xmx4096m > -XX:-UseGCOverheadLimit Can you try increasing these vm memory params and check whether it works?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
This bug has been marked as stalebug a while ago without any further interaction. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard flag.
