Bug 270364 - Freeze when a thread is blocked on System.in.read()
Summary: Freeze when a thread is blocked on System.in.read()
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-28 18:31 EDT by Christopher Deckers CLA
Modified: 2019-09-06 16:13 EDT (History)
1 user (show)

See Also:

Attachments
The browser freeze and the Program.getImageData() freeze (2.93 KB, text/x-java)
2009-03-28 18:31 EDT, Christopher Deckers CLA 		no flags Details
View All 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 Christopher Deckers CLA 2009-03-28 18:31:37 EDT 
Created attachment 130172 [details]
The browser freeze and the Program.getImageData() freeze

Build ID: 3.5M6

Steps To Reproduce:
1. Have a thread reading from System.in
2. Create a Browser or get the image data of a program -> it freezes.

More information:
- The browser freeze happens whether IE or XULRunner is used.
- Creating a shell or a button works fine.
- It is unclear how many other such cases are affected.
- Everthing seems to work fine on Linux.

Allowing some data to be read from System in is important and I am not sure whether there is a workaround for this bug.
Comment 1 Felipe Heidrich CLA 2009-03-30 10:36:56 EDT 
Works for me (button 1 and button 2).
Comment 2 Christopher Deckers CLA 2009-03-30 13:58:05 EDT 
(In reply to comment #1)
> Works for me (button 1 and button 2).

After some more tests, it seems that the problem appears when launching the sample from within Eclipse... Do you happen to know what difference it makes?

The problem is that we need this capability as part of a component which may be used from Eclipse.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:13:57 EDT 
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.