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

Bug 361011

Summary: Freeze after web project refresh
Product: [WebTools] WTP Source Editing Reporter: Victor Homyakov <vkhomyackov>
Component: jst.jspAssignee: jst.jsp <jst.jsp-inbox>
Status: RESOLVED WORKSFORME QA Contact: Nick Sandonato <nsand.dev>
Severity: normal    
Priority: P3 CC: thatnitind
Version: unspecifiedKeywords: performance
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Attachments:
Description Flags
Thread dump
none
Thread dump after 20 minutes
none
Still hangs none

Description Victor Homyakov CLA 2011-10-14 13:14:15 EDT
Build Identifier: 

Eclipse was frozen after project refresh (refresh was needed because some CSS and JSP files were changed outside of Eclipse).

Reproducible: Sometimes

Steps to Reproduce:
1. Create Web project (~350 JSP files).
2. Change some CSS and JSP files.
3. In Eclipse Project explorer press F5 on project.

I think it is related to WTP because of thread dump (the only one runnable thread stays in org.eclipse.jst.jsp package).
Comment 1 Victor Homyakov CLA 2011-10-14 13:15:49 EDT
Created attachment 205221 [details]
Thread dump

Thread dump while Eclipse hangs.
Comment 2 Victor Homyakov CLA 2011-10-14 13:18:34 EDT
Created attachment 205223 [details]
Thread dump after 20 minutes

Eclipse still hangs after 20 minutes.
Comment 3 Victor Homyakov CLA 2011-10-15 05:39:37 EDT
Created attachment 205245 [details]
Still hangs
Comment 4 Nitin Dahyabhai CLA 2011-10-19 17:01:40 EDT
During that time, was CPU usage near zero or did it seem to still be "working"?
Comment 5 Victor Homyakov CLA 2011-10-20 04:21:21 EDT
(In reply to comment #4)
> During that time, was CPU usage near zero or did it seem to still be "working"?

near 50% (45%-49%) on Pentium E2200 (dual core)
Comment 6 Nitin Dahyabhai CLA 2011-10-24 11:05:01 EDT
Victor, as with bug 359569, can you confirm which version of the org.eclipse.jst.jsp.core plug-in is installed, as well as whether the workspace and all libraries/jars you are referring to from it, are on a local disk (not a mounted network or other removable filesystem)?
Comment 7 Victor Homyakov CLA 2011-10-25 04:06:10 EDT
(In reply to comment #6)
> which version of the org.eclipse.jst.jsp.core plug-in
> is installed

org.eclipse.jst.jsp.core_1.2.401.v201108302147.jar  654823 bytes

> whether the workspace and all libraries/jars you're
> referring to from it are on a local disk (not a mounted network or removable
> filesystem)?

Eclipse, workspace and all other jars are located on the same local disk, on
the same partition (exactly: ~/bin/eclipse-3.7, ~/workspace, ~/.m2/repository).
All required libraries are placed either in workspace or in maven local
repository.
Comment 8 Nick Sandonato CLA 2013-01-14 17:32:47 EST
Victor, thanks for these stack traces. Did this problem continue afterwards? I haven't seen anything like this myself, and the stack traces haven't uncovered anything too particularly glaring to me. I know it's been a little while, but maybe there's something that could help pinpoint the problem.
Comment 9 Victor Homyakov CLA 2013-01-16 01:15:39 EST
> Did this problem continue afterwards?
> I haven't seen anything like this myself

I've upgraded to Eclipse 3.8 (then to 3.8.1) + SVN 1.7, and it isn't freezing anymore. Actually, any project refresh goes much faster than with Eclipse 3.7.2 + SVN 1.5.

Maybe this problem was related to SVN, because SVN prior to 1.7 was creating .svn folder and files in each subdirectory, and problematic project had complex directory structure?
Comment 10 Nick Sandonato CLA 2013-01-17 17:50:26 EST
(In reply to comment #9)
> > Did this problem continue afterwards?
> > I haven't seen anything like this myself
> 
> I've upgraded to Eclipse 3.8 (then to 3.8.1) + SVN 1.7, and it isn't
> freezing anymore. Actually, any project refresh goes much faster than with
> Eclipse 3.7.2 + SVN 1.5.
> 
> Maybe this problem was related to SVN, because SVN prior to 1.7 was creating
> .svn folder and files in each subdirectory, and problematic project had
> complex directory structure?

Thanks for the update. Since I haven't been able to reproduce, and you've been having a better experience as well, I'm going to resolve this. However, if you notice it springing up again, we can revisit the issue.