| Summary: | Submitting to bugzilla may freeze eclipse | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Peter Kullmann <peter.kullmann> | ||||
| Component: | Mylyn | Assignee: | Mylyn Inbox <mylyn-inbox> | ||||
| Status: | RESOLVED DUPLICATE | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | Macintosh | ||||||
| OS: | Mac OS X | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Peter Kullmann
To investigate further we would need a stack trace. You can try using jps and jstack from a shell to capture one at the moment the freeze happens? Unfortunately, after the freeze eclipse no longer appears in jps. I will try jstack nonetheless the next time. I have some other similar issues where the refresh of the task editor seems to hang. Now I have noticed that bringing another app to the foreground and then switching back to eclipse helps the editor along. So perhaps my problem is a SWT/Cocoa issue. You could also try increasing the MaxPermSize or memory pool in case Eclipse crashes due to a lack of resources. Created attachment 202607 [details]
jstack output of a frozen eclipse instance
It happened again and this time I was able to create a jstack dump. As one can see it stops at handling the tree click (I again accidentally clicked the task list tree during submit).
Thanks. That looks like bug 344818. I would recommend posting the stack trace there with any hints to the SWT team how to reproduce the condition. *** This bug has been marked as a duplicate of bug 344818 *** |