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

Bug 316231

Summary:

App intermittently hangs when closing with Rational function tester

Product:

[Eclipse Project] Platform

Reporter:

yanghang

Component:

SWT

Assignee:

Felipe Heidrich <eclipse.felipe>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

normal

Priority:

CC:

mukund, raji, Silenio_Quarti

Version:

4.0

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

stalebug

Attachments:

Description	Flags
the sample code	none
hover text image	none
business card image	none
libs used in my app, it is too big, just attached the image	none

Description yanghang

2010-06-08 21:52:27 EDT

Build Identifier: 

The Rational Functional Tester code is simply trying to call .close() against any org.eclipse.swt.widgets.Shell class found in the Java domain.  During a find, 3 shells are found:
The Sametime Connect main window
The business card
The hover text


The Rational Functional Tester code eliminates the Sametime Connect main window as a candidate for close and then progresses to close the business card and hover text, based upon their class design.  There are currently no attribute that can be used to distinguish the hover text shell from for example an open preferences shell based upon the design today.  When close is called against an open business card, the .close() does not hang the entire JVM.  However, when .close() is called against the hover text, the entire JVM hangs.  I believe this is based upon an improper implementation of the shell itself being used for the hover text.  The hover text shell never calls shell.open(), thus any .close() calls that later come along results in a hang of the entire JVM.


I attached the sample code, it includes the SWT package we used.


Reproducible: Sometimes

Steps to Reproduce:
Use Rational Functional Tester script to do operations below
1. start the app;
2. use click() to change focus on tree, make the bussiness card and hover text out;
3. to close the App
4. the app intermittently  hangs

Comment 1 yanghang

2010-06-08 22:06:17 EDT

Created attachment 171485 [details]
the sample code

it is sample code, the tree includes business card, and hover text, they both implement with shell.

Comment 2 yanghang

2010-06-08 22:07:01 EDT

Created attachment 171486 [details]
hover text image

Comment 3 yanghang

2010-06-08 22:07:33 EDT

Created attachment 171487 [details]
business card image

Comment 4 yanghang

2010-06-08 22:10:04 EDT

Created attachment 171488 [details]
libs used in my app, it is too big, just attached the image

Comment 5 Silenio Quarti

2010-06-10 10:58:02 EDT

Felipe, please investigate this bug

Comment 6 Felipe Heidrich

2010-06-10 11:28:03 EDT

I can't reproduce the problem on my machine. Please explain the steps to reproduce the problem with more details.

On my machine, when the main windows is up, if I stop the mouse over the first item (Manager) it shows a tooltip. If I stop the mouse over any other item it shows a window (which you call business card, I suppose), if a move the mouse the business card window closes.

Comment 7 Raji Akella

2010-06-10 11:59:32 EDT

Will get Lotus Sametime team to help you.

Comment 8 Eclipse Webmaster

2019-09-06 16:14:50 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.

Comment 9 Eclipse Genie

2022-02-08 12:19:10 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.