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

Bug 108321

Summary:

running valid unsaved program makes console gray out

Product:

[Eclipse Project] JDT

Reporter:

Martin Olsson <mnemo>

Component:

Debug

Assignee:

Kevin Barnes <cocoakevin>

Status:

RESOLVED DUPLICATE

QA Contact:

Severity:

normal

Priority:

CC:

andrew

Version:

3.1

Target Milestone:

3.2 RC1

Hardware:

OS:

Windows 2000

Whiteboard:

Bug Depends on:

84885

Bug Blocks:

Attachments:

Description	Flags
grayed out console	none

Description Martin Olsson

2005-08-29 17:11:40 EDT

Add a comment to a simple hello world program
and run it before it's saved. Eclipse prompts
for save before run, accept save all. Now program
runs and the output is seen for a short moment in
the console; however after 300-500ms the console
goes completely gray and the program output is no
longer seen.

Comment 1 Olivier Thomann

2005-08-30 08:00:45 EDT

Move to JDT/Debug.

Comment 2 Darin Wright

2005-08-30 10:38:50 EDT

Can you attach a screen shot?

Comment 3 Martin Olsson

2005-09-01 12:53:20 EDT

First off, I've also found that the console only grays out if the program
finishes very quickly.

Below is a 30mb zipped .mpg video showing my screen as I explain the problem:
http://mnemo.minimum.se/screens/console_goes_gray.zip

I'm also going to attach a screenshot showing the grayed out console.

Comment 4 Martin Olsson

2005-09-01 12:53:52 EDT

Created attachment 26762 [details]
grayed out console

Comment 5 Darin Wright

2005-09-02 11:10:55 EDT

*** Bug 108645 has been marked as a duplicate of this bug. ***

Comment 6 Darin Wright

2005-09-16 12:17:01 EDT

This has to do with the interaction of the "dummy launch" we create when a 
build is performed at launch time. Because a file has been saved/changed, this 
triggers a build, so a "launch placeholder" is added to the launch view. It 
appears the be a timing issue where the dummy launch is being added, but the 
real launch is already complete/terminated, and thus the real launch with 
output is removed. This should be fixed in conjunction with bug 84885.

Comment 7 tuanglen

2005-11-29 03:07:38 EST

I installed Eclipse for the first time, everything default, typed the standard Java Hello, World test app in what looked like the editor, clicked what looked like a "Run" button, and immediately encountered this bug. Thirty seconds of the most obvious possible use of a Java IDE and bang! I've found a bug in Eclipse. 

If brand new users of an app I wrote tended to encounter a bug within the first thirty seconds after installation by doing exactly what they would be expected to do, I'd consider it a bug worth fixing even if it weren't a crasher.

Comment 8 jwisetech

2005-12-15 14:01:02 EST

FYI - I didn't see any mention of a temporary workaround; here are the steps I do to get back to a working console.
1) Close the console view
2) Shutdown the IDE.
3) Reopen the IDE
4) Select a project and run it. 

This action re-opened the console view and all is back to normal. 

HTH

My Environment:
Version: 3.1.0
Build id: I20050627-1435
MyEclipse plug-in

Comment 9 Darin Wright

2006-04-04 17:54:35 EDT

Also see bug 128452

Comment 10 Kevin Barnes

2006-04-05 13:12:32 EDT

I suspect this one is fixed with bug 128542, but I haven't been able to reproduce either locally.

Comment 11 Kevin Barnes

2006-04-07 12:35:09 EDT


*** This bug has been marked as a duplicate of 128452 ***