Bugzilla – Full Text Bug Listing
| Summary: | Eclipse completely locks up due to an XML file in task context | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Jörg Thönnes <jtk499> | ||||||||||||||
| Component: | Mylyn | Assignee: | Mik Kersten <mik.kersten> | ||||||||||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||||||||||
| Severity: | critical | ||||||||||||||||
| Priority: | P3 | ||||||||||||||||
| Version: | 2.0 M1 | ||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Hardware: | PC | ||||||||||||||||
| OS: | Linux | ||||||||||||||||
| Whiteboard: | |||||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
Jörg Thönnes
This took me half a day: On every eclipse start with the culprit task activated or activating the task sometimes locks up the UI completely. Doing several thread dumps with jstack showed no difference, so the eclipse seemed to be really locked up. I suspect an XML file being part of the task context (package explorer and outline view open) as the culprit. Today I did a number of experiments with a clean workspace and the XML file alone, but it worked fine. Actually, I do not have more time to look at this, but it is really, really a show stopper. Therefore, I try to rise priority. I would really appreciate if the Mylar team could look at this. Possibly, its an WST or Eclipse core issue. So please feel free to forward this bug. My knowledge of internals is too limited. Created attachment 62182 [details]
First lockup stack trace
Doing several jmap <pid> calls always showed this stack trace.
No differences --> lockup.
Created attachment 62183 [details]
Second lockup stack trace
Doing several jmap <pid> calls always showed this stack trace.
No differences --> lockup.
Second example, maybe the pattern is different (or the same).
Created attachment 62184 [details]
Console output showing event loop exceptions
Some the lockup breaks and an exception log appears at stdout.
This is an exception log showing an event loop.
Created attachment 62185 [details]
Console output showing IndexOutOfBounds
This console output shows an IndexOutOfBounds error.
If I remember correctly, the lockup broke here.
Finally, I cleaned up by deleting the context of the culprit task and checked whether none of the Mylar XML contains references to the "poisoned" XML file. But not sure whether XML file is the culprit. Do you need my lockup Mylar context, too? It may contain proprietary infos, so would like to clean up before. Created attachment 62186 [details]
XML possibly causing the issue
This XML file possibly caused this issue. It switched to another CVS branch on it with Package Explorer and Outline View enabled.
But I could not reproduce using this file alone. So I may be wrong and a more complex interaction is the reason.
I fixed this last week on Eclipse 3.3 and still need to merge it back to Eclipse 3.2. A 3.2 dev build will be available this evening from the 3.2 update site: http://www.eclipse.org/mylar/dl.php If you still see this bug with the dev build please reopen. (In reply to comment #8) > I fixed this last week on Eclipse 3.3 and still need to merge it back to Eclipse > 3.2. A 3.2 dev build will be available this evening from the 3.2 update site: > http://www.eclipse.org/mylar/dl.php Thank you very much, Mik. This actually led me to the point were I considered stop using Mylar for the moment. This would be very sad, since I love to use it. Just curious: Could you provide some background on the bug? (In reply to comment #9) > If you still see this bug with the dev build please reopen. Will do. What was happening is that a refresh job for the progress bar on the Task List was running whether or not the workbench was running. Please note that a 3.2 build is not available yet, but will be available later today. (In reply to comment #11) > What was happening is that a refresh job for the progress bar on the Task List > was running whether or not the workbench was running. I will import the Mylar export with the culprit task context and see what happens... > Please note that a 3.2 build is not available yet, but will be available later > today. Hmmm, are you talking about (a) 2.0M2 on http://download.eclipse.org/technology/mylar/update-site/e3.2 or (b) http://download.eclipse.org/technology/mylar/update-site/dev/e3.2 How save is it to use option (b)? Cheers, Jörg When I refer to dev builds I refer to option (b). Using dev builds is generally as safe as using releases: http://wiki.eclipse.org/index.php/Mylar_User_Guide#Releases Fyi Mylar committers tend to work straight from HEAD. Created attachment 62553 [details]
jstack trace from completely frozen Eclipse
Today (before the next Mylar dev build) I got again a lock-up.
Looking at the stack trace, do you think it is related?
Joerg: no, this does not look related to me., it looks like a bug that we fixed shortly after that dev build went out. We'll have a dev build available again in about 20min. |