Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 361220

Summary:	Default console type should be selectable (or CDT global build console should be default to use)
Product:	[Tools] CDT	Reporter:	Andrey Grigoriev <f0r_spam>
Component:	cdt-build	Assignee:	cdt-build-inbox <cdt-build-inbox>
Status:	NEW ---	QA Contact:	Jonah Graham <jonah>
Severity:	normal
Priority:	P3	CC:	cdtdoug, mikhail.barg, yevshif
Version:	8.0
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Andrey Grigoriev

2011-10-18 04:44:15 EDT

Build Identifier: 20110916-0149

When Eclipse is started the "CDT build console" is used to show build process output and after several builds it starts to cause terrible slowdowns (Eclipse stops responding for dozens of seconds) when I browse through different projects in project manager.

These slowdowns are eliminated when I switch to "CDT global build console". But I have to switch to it every time I start Eclipse: there is no option to set it as default console to use and selected console is not saved on exit.

Reproducible: Always

Steps to Reproduce:
1. Start Eclipse
2. Open Console view
3. Notice that "CDT build console" is shown.
4. Choose "CDT global build console".
5. Close Eclipse.
6. Start it again.
7. Notice that "CDT build console" is set back.

Comment 1 Andrew Gvozdev

2011-10-18 10:53:20 EDT

In my opinion, it is unlikely that using global console vs project console would make a difference, it could be accidental. Can you generate a thread dump when eclipse stops responding and attach it to the report?

Comment 2 Andrew Gvozdev

2011-10-18 10:56:14 EDT

(In reply to comment #1)
> In my opinion, it is unlikely that using global console vs project console would
> make a difference, it could be accidental. Can you generate a thread dump when
> eclipse stops responding and attach it to the report?
See http://wiki.eclipse.org/How_to_report_a_deadlock about generating thread dump.

Comment 3 Andrey Grigoriev

2011-10-18 12:11:54 EDT

That doesn't cancel the fact that despite having two consoles I can't set up which I want to use.

The freezing Eclipse is a separate issue and it is quite definitely connected to the console selected: I'm observing it for quite some time already and it seems to be somehow connected with switching individual build consoles when clicking a file in other project in project manager. 

Introducing global build console in CDT 8 made that switches instant (when this console is selected). 

I'll get the thread dump as soon as I'll be able to reproduce the issue.

Comment 4 Andrey Grigoriev

2011-10-18 12:15:44 EDT

BTW, clearing the project build consoles eliminates the issue for some time.

Comment 5 Andrew Gvozdev

2011-10-18 14:12:02 EDT

(In reply to comment #3)
> That doesn't cancel the fact that despite having two consoles I can't set up
> which I want to use.
> The freezing Eclipse is a separate issue and it is quite definitely connected to
> the console selected:
I agree, they are different issues. It would be best if you open another report for freezing issue to keep this one dedicated to the option to keep global console by default.

Comment 6 Mikhail Barg

2011-10-19 04:50:57 EDT

The setting for choosing global build console as default was requested long time ago here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=309113#c14

I also think it would make things more usable for multi-project builds.

Comment 7 Andrey Grigoriev

2011-10-19 08:24:14 EDT

Here you go: https://bugs.eclipse.org/bugs/show_bug.cgi?id=361383 freezing eclipse issue.