Bug 44344 - [Widgets] Mouse grab causes update problems
Summary: [Widgets] Mouse grab causes update problems
Status: CLOSED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.0   Edit
Hardware: PC Linux-GTK
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Felipe Heidrich CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 43844
  Show dependency tree
 
Reported: 2003-10-07 14:32 EDT by Douglas Pollock CLA
Modified: 2016-10-18 10:56 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Douglas Pollock CLA 2003-10-07 14:32:19 EDT
This is a bit of an arcane problem.  Bug40023Test.java
(org.eclipse.ui.tests/Eclipse UI Tests/org.eclipse.ui.tests.keys) fails
intermittently through what appears to be a failure to update the state of the
GUI.  The problem occurs with Eclipse-GTK-I20031007/GNOME/Metacity/RedHat9.

The failure occurs at least once every ten executions, sometimes much more.

I believe the problem is tied into x2vnc.  When x2vnc is running on the machine
running the tests, the test suites will fail intermittently.  When it is not
running, then the tests always pass.  The test suites also pass on a machine
running a vncserver to which x2vnc is connected.

My hypothesis (gut-feeling) is that the problem is somehow tied into the
XGrabPointer, XGrabKeyboard, and XFlush calls when x2vnc tries to trap the mouse
for forwarding to the vncserver.  So, while the specific symptom I see is
specific to x2vnc, I think the problem might occur in other applications where
these functions are called.

If you need to see the problem first-hand, please stop by my desk.
Comment 1 Douglas Pollock CLA 2003-10-08 10:25:02 EDT
I've know figured out how to reproduce consistently.  Move the mouse to the
other machine while the test suite runs.

I imagine you could write a small grabber application that just does a
XGrabPointer/XGrabKeyboard for a fixed time and then releases it.  Start the
test suite, and then immediately run the grabber application.  If my hunch is
right, that should cause the failure.
Comment 2 Douglas Pollock CLA 2003-10-08 12:57:33 EDT
Bug 43312 is most likely related to this bug.  I believe it provides another
reproducible test case, but ending in a segmentation fault.
Comment 3 Felipe Heidrich CLA 2009-08-17 16:48:24 EDT
Your bug has been moved to triage, visit http://www.eclipse.org/swt/triage.php for more info.
Comment 4 Eric Williams CLA 2016-10-18 10:56:24 EDT
No response in awhile, also no specific steps to reproduce. I'm going to go ahead and close this, please feel free to re-open if the issue persists.