Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 333395

Summary: subclipse crashes when in Helios, but works under Galileo when expanding a repository.
Product: [Eclipse Project] Platform Reporter: fuzzballz
Component: TeamAssignee: Platform Team Inbox <platform-team-inbox>
Status: RESOLVED NOT_ECLIPSE QA Contact:
Severity: critical    
Priority: P3 CC: remy.suen, tomasz.zarna
Version: 3.6.1   
Target Milestone: ---   
Hardware: PC   
OS: Linux-GTK   
Whiteboard:
Attachments:
Description Flags
Helios config file from about none

Description fuzzballz CLA 2011-01-03 00:12:05 EST
Build Identifier: M20100909-0800

After installing a fresh JDE or Classic copy of eclipse and then installing the latest subclipse.  When you open the SVN Respository explorer and try to expand a repository, Eclipse says pending for a few seconds then crashes catastrophically.  It saves no data, writes no error logs.  Using the same version of subclipse with an updated Galileo  works perfectly for the same repository. This happens whether I use the 1.6.11 javahl or the SVN kit native adapter.
System detail Mandriva Linux 2.6.33.7-desktop-2mnb #1 SMP Mon Sep 20 18:19:20 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux with a KDE plasma desk top running on a quad-core intel.





Reproducible: Always

Steps to Reproduce:
1.Download and expand latest Helios JDE or Classic
2.install subversive minimal or complete option
3.register a repository
4.attempt to expand repository tree.
Comment 1 fuzzballz CLA 2011-01-03 00:25:05 EST
Created attachment 185941 [details]
Helios config file from about
Comment 2 Tomasz Zarna CLA 2011-01-03 05:26:17 EST
It doesn't look like a Team issue, I suggest you open a new bug against Subclipse (http://subclipse.tigris.org/servlets/ProjectIssues).
Comment 3 fuzzballz CLA 2011-01-03 13:05:07 EST
Why does it work with Galileo and not Helios?
Comment 4 Remy Suen CLA 2011-01-03 22:21:19 EST
Do you get the problem if you try to navigate through CVS repositories?

We can't really comment on the problem without more information (such as your workspace's logs and/or VM crash logs).