| Summary: | A lot of threads | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Community | Reporter: | Pascal Rapicault <pascal> | ||||
| Component: | Cross-Project | Assignee: | Cross-Project issues <cross-project.inbox> | ||||
| Status: | RESOLVED DUPLICATE | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | steffen.pingel | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Pascal Rapicault
Created attachment 126102 [details]
VM dump
Mylyn still uses a single TimerThread in version 3.0.x which probably shows up in the stack dump. All usages of java.util.Timer in Mylyn will be replaced by jobs for the next release (and Galileo): bug 233590. Given that I'm using Mylyn 3.1 20090202, the threads I am seeing are probably the Mylyn ones. Closing as a dupe for now. *** This bug has been marked as a duplicate of bug 233590 *** |