| Summary: | [Compatibility] Timer execs greatly affect XWindow based systems | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] e4 | Reporter: | Eric Moffatt <emoffatt> | ||||
| Component: | UI | Assignee: | Eric Moffatt <emoffatt> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | critical | ||||||
| Priority: | P3 | CC: | carolynmacleod4, pwebster, remy.suen | ||||
| Version: | unspecified | Flags: | emoffatt:
review?
|
||||
| Target Milestone: | 4.1 RC4 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Eric Moffatt
Created attachment 197100 [details]
Gather up all the items to be checked rather than spawning a new timerExec for each one
Paul, please review the patch... I've only made one slight change. The HCI can create one instance of the safe runnable, instead of one per call, since it contains no state and doesn't change. Committed to HEAD. Remy, could you also have a quick look at what I've committed as a confirmation? PW (In reply to comment #3) > Committed to HEAD. Remy, could you also have a quick look at what I've > committed as a confirmation? Looks okay to me. Marking as FIXED. Verified in I20110604-2201. |