Bug 50490

Summary: Eclipse 3.0M6 hang on rename of package
Product: [Eclipse Project] JDT Reporter: Rob Grzywinski <rgrzywinski>
Component: CoreAssignee: JDT-Core-Inbox <jdt-core-inbox>
Status: RESOLVED INVALID QA Contact:
Severity: blocker    
Priority: P3    
Version: 3.0   
Target Milestone: 3.0 M7   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
Stack traces while renaming packages
none
VM thread dump on hang none

Description Rob Grzywinski CLA 2004-01-23 14:12:33 EST 
While I was renaming a number of packages Eclipse 3.0M6 would hang requiring me 
to kill the process via the Task Manager.  The ability to reproduce this is 
spotty but it seems it can be reproduced by *quickly* renaming a number of 
packages (rename a package, then quickly renmae another).

I should mention that I am using p4eclipse 0.6.2 but the packages were NOT 
checked in to the repository and they were not read only.  I should also metion 
that this hang occurred once on a package that contained no files.

Stack traces will be attached.
Comment 1 Rob Grzywinski CLA 2004-01-23 14:16:56 EST 
Created attachment 7544 [details]
Stack traces while renaming packages

Some stack traces may be spurious as I did no clean up between having to kill
eclipse from one rename to another and it may be that only some files were
copied.
Comment 2 Philipe Mulet CLA 2004-01-23 15:49:57 EST 
These are entries from the log, but could you please launch Eclipse with 
console open, and then press ctrl-break to force the VM to dump thread 
activity. This would allow to point at the code which is causing the hang.

Launch Eclipse using java.exe instead of javaw.exe to get console open.
Comment 3 Rob Grzywinski CLA 2004-01-23 15:59:16 EST 
Created attachment 7546 [details]
VM thread dump on hang

Renamed 1 package then quickly renamed another.
Comment 4 Philipe Mulet CLA 2004-01-23 16:07:19 EST 
It looks like Perforce is creating the locking condition.
Comment 5 Rob Grzywinski CLA 2004-01-23 16:25:29 EST 
That is all well and good, and I'm not looking for you to solve someone else's 
problem, but I believe that every problem can lead to a better solution.  Are 
you able to easily determine which component that Perforce is improperly 
interacting with so that I may contact them?  I would like to ensure that the 
proper documentation is available for projects coded against Eclipse so that 
this bug is prevented in the future.

Thank you.
Comment 6 Philipe Mulet CLA 2004-01-24 09:35:37 EST 
If you send them the thread dumps, they should be able to figure their bug.
Will close this one.