| Summary: | [StyledText] [misc] Scrolling a text editor is painfully slow when using Remote Desktop | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Andrey Tarantsov <andreyvit> | ||||
| Component: | SWT | Assignee: | Platform-SWT-Inbox <platform-swt-inbox> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Felipe Heidrich <eclipse.felipe> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | daniel_megert, ericwill, snorthov | ||||
| Version: | 3.3 | Keywords: | triaged | ||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows All | ||||||
| Whiteboard: | stalebug | ||||||
| Attachments: |
|
||||||
|
Description
Andrey Tarantsov
First we need some more info: 1. which build id? 2. which editor? 3. please try with the attached SWT snippet 4. create a stack trace while it scrolls and attach it here Created attachment 75635 [details]
ScrollTest snippet
Please reopen with more data. Actually it's still slow with the snippet, but I cannot get a stack trace because the remote desktop does not process any input while scrolling has not completed. Chances are Eclipse is not doing anything at this point, but somehow it has created too many screen updates that somewhy do not get dropped. I'm using Microsoft Remote Desktop 2 beta, but the problem also occurs with Remote Desktop 1.0.3. I tried filing the bug over it, but they refused to accept it because it is only reproducible with Eclipse. Using SWT 3.3.0.v3346 - the one available on Europa release day. Ideas? Microsoft Connect bug URL: https://connect.microsoft.com/macrdc/feedback/ViewFeedback.aspx?FeedbackID=290344 (but there's not much to see there) >Actually it's still slow with the snippet,
Moving to SWT for comment.
Your bug has been moved to triage, visit http://www.eclipse.org/swt/triage.php for more info. Moving to Windows. Bug triaged, visit https://wiki.eclipse.org/SWT/Devel/Triage for more inforamation. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |