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

Bug 23377

Summary:	OS Crashes when sharing a new CVS repository
Product:	[Eclipse Project] Platform	Reporter:	Tony Lagnada <tony>
Component:	Team	Assignee:	Kevin McGuire <Kevin_McGuire>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	critical
Priority:	P3	CC:	tony
Version:	2.0.1
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Tony Lagnada

2002-09-10 13:18:27 EDT

This issue occurs initially when creating a new share on a CVS repository.
CVS Repository is on RedHat Linux (never had issues with Eclipse before).

This issue is repeatable.

OS:  Windows XP
CPU:  AMD Athlon XP 2200+ (standard config, not overclocked)
CPU Mem:  512MB
JDK:  Sun j2sdk1.4.0_01 (Installed via installer)
CVS Server:  Running on remote host (RedHat Linux 7.2 standard cvs server)

Eclipse Version: 2.0.2, no other plugins installed.

Description of Events:

1.  Switch to CVS Repository Exploring perspective
2.  Select a project that has not been created in CVS
3.  Right-click the project and select "Team->Share project..." on the
popup menu.
4.  The share project popup dialog comes up and m cvs repository is selected.
5.  I select the "use specified module name" and enter a path similar to
this:  /my/cvs/module
6.  Click Finish

Eclipse tries to add the project and then crashes my machine.
I then check my cvs server on linux and turns out that only the parent
project dir was created before it crashed.

Work-around:

Use an external CVS client to add a new cvs module, then retrieve the module
in Eclipse.

Comment 1 Olivier Thomann

2002-09-10 13:41:57 EDT

Move to Platform/VCM.

Comment 2 Michael Valenta

2002-09-10 14:00:03 EDT

Does your machine have a linksys network card (see bug 21276)?

Comment 3 Tony Lagnada

2002-09-10 14:06:40 EDT

Right on...Yes I have a LINKSYS card.

Craps...I tried to get rid of my Netgear card because it was crashing
Samba...anyways...that's a personal issue.

Kevin, I'm closing this issue.
Reason:  (duplicate bug of #21276).

*** This bug has been marked as a duplicate of 21276 ***