Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 363817 - Performance degradation over time when console output unlimitted
Summary: Performance degradation over time when console output unlimitted
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-15 08:23 EST by Yoakim Anastasov CLA
Modified: 2019-11-14 03:48 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yoakim Anastasov CLA 2011-11-15 08:23:46 EST 
Build Identifier: 20110615-0604

The console output performance degrades seriously over time after the console output is unlimitted. Restarting the IDE does NOT fix the problem. The period of time most probably depends on the number of outputted lines, for me it's about 1 week with IDE restart every day.
Known workaround: recreate workspace.

Reproducible: Always

Steps to Reproduce:
1. Uncheck "Limit console output" in Window -> Preferences -> Run/Debug -> Console
2. Run/debug application in eclipse which prints in std out/err
Comment 1 DJ Houghton CLA 2011-11-15 08:30:41 EST 
This is very strange. I have had my console options set to unlimited output for years but never run into this myself. Especially strange since I don't believe console output is kept across IDE invocations. Moving to Debug for comment.
Comment 2 Lars Vogel CLA 2019-11-14 03:48:39 EST 
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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.