| Summary: | Console causes v. high CPU usage when v. long line is outputted. | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Peter Smith <pesmith> |
| Component: | Debug | Assignee: | Platform-Debug-Inbox <platform-debug-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | cheryladams, pesmith |
| Version: | 3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Peter Smith
What version of Eclipse and which JDK are you using? How long does Eclipse become unresponsive? Does it recover? Are the contents of the console correct once they have been displayed? Tested on I20050104-1600 and everything was responsive with fixed width option both on and off. I have tried again with build I20050104-1600 the rendering appears to be OK for a fixed widths but it is still very unresponsive for no fixed width for very long lines. Try lines of length around 100,000 characters and more. It happens on all the following JVMs: jdk1.5 jdk1.4.2 jrockit1.5 Just curious - is the output actually intended to be read by humans? If not, you might want to direct the output to a file instead (see the Common tab of the launch config). In this case each line of output is intended to be read by developers for debugging purposes (its request/response pairs from client/server in an application) although in practice its usually only the first few hundred and last few hundred that will be looked at. The fixed width is a workaround but not a very nice one as we are intentionally dumping out single lines. A review of the console's performance is already on the schedule. The current work arounds are to output to a file instead of the console, or use a fixed width. *** This bug has been marked as a duplicate of 78166 *** |