Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365579 - m2e is very slow opening a workspace
Summary: m2e is very slow opening a workspace
Status: CLOSED INVALID
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-05 07:35 EST by Kabir Khan CLA
Modified: 2021-04-19 13:22 EDT (History)
2 users (show)

See Also:

Attachments
Log file so far (305.71 KB, text/plain)
2011-12-05 07:37 EST, Kabir Khan CLA 		no flags Details
A few thread dumps happening while setting classpath containers (85.27 KB, text/plain)
2011-12-05 07:37 EST, Kabir Khan CLA 		no flags Details
Second part of log (16.37 KB, text/plain)
2011-12-05 07:39 EST, Kabir Khan CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kabir Khan CLA 2011-12-05 07:35:03 EST 
Build Identifier: 1.0.100.20110804-1717

It seems to be doing stuff but is very slow in the "Setting classpath containers" stage, CPU = 100%.
I'll attach the full log and a few thread dumps once this build either hangs forever or completes.
This version of m2e seems to be a lot slower than the one I had until I upgraded last week.

Reproducible: Sometimes

Steps to Reproduce:
I have had it working fine but only when I cleaned out my workspace
Comment 1 Kabir Khan CLA 2011-12-05 07:37:20 EST 
Created attachment 207914 [details]
Log file so far
Comment 2 Kabir Khan CLA 2011-12-05 07:37:56 EST 
Created attachment 207915 [details]
A few thread dumps happening while setting classpath containers
Comment 3 Kabir Khan CLA 2011-12-05 07:39:51 EST 
Created attachment 207916 [details]
Second part of log
Comment 4 Kabir Khan CLA 2011-12-05 07:40:48 EST 
Once it got through the "Setting classpath containers" stage it completes quite fast.
Comment 5 Igor Fedorenko CLA 2011-12-05 07:52:14 EST 
I appreciate the problem but provided information is not enough to begin investigation. From the thread dump it appears that workspace build is running and this is generally not expected after clean workspace restart. Unfortunately, it is impossible to tell what triggered workspace build and if the build is actually causing the performance problem.
Comment 6 Kabir Khan CLA 2011-12-05 07:57:25 EST 
Starting with a clean workspace works better as it did last week. What information can I provide to help next time this happens?
Comment 7 Kabir Khan CLA 2011-12-05 09:25:36 EST 
I'm downgrading to 1.0.0, 1.0.100 is unusable for me. I'm not 100% sure when the error happens but it seems to be when reopening a workspace (the initial import is fine)
Comment 8 Igor Fedorenko CLA 2011-12-05 09:55:25 EST 
Be "clean" I meant the workspace was shutdown cleanly and there were no direct filesystem changes to the project sources, i.e. you did not run maven build on command line. Both killing Eclipse instance and making direct filesystem changes will trigger rebuild after workspace restart.
Comment 9 Igor Fedorenko CLA 2012-05-21 10:31:52 EDT 
Closing old/stale bugreports.
Comment 10 Denis Roy CLA 2021-04-19 13:22:23 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/