Community
Participate
Working Groups
I'm not sure how reproducible this bug is. I was debugging a self-hosted workbench through a JUnit plug-in test. A patch was neeeded, so I clicked on the team synchronize perspective. A segfault occurred before any perspective change occurred -- killing both the self-hosted windows and the Eclipse windows. The machine config is: RedHat 9, Eclipse-GTK-I20030917, GNOME, gtk2-2.2.1-4.
Created attachment 6155 [details] core dump
Created attachment 6173 [details] Another core dump Another core dump. This time while trying to double-click on an item in the Team Synchronizing perspective to get it do a compare. Eclipse-GTK-I20030917. Not easily reproducible, but this seems to be more than a rare occurrence. Running UiTestSuite sometimes crashes in the same way.
Doug, if you find more scenarios where this happens then please add them to this report.
Created attachment 6271 [details] core dump #3 (running UiTestSuite in platform-ui) This should hopefully make things a bit more reproducible for you. This occurred while running the UiTestSuite for platform-ui. It is available in CVS in the project "org.eclipse.ui.tests". The failure occurred on consecutive runs, on tests #192 and #186, respectively. Using Eclipse-GTK-I20030925
Created attachment 6340 [details] core dump while jumping to test suite failure This looks different than the other three. This might be unrelated. If it is, could you file another bug and CC me. Thanks.
Created attachment 6369 [details] while running ShowViewTest.test1() Another failure while running the UiTestSuite.
I've run the test suite twice without using x2vnc, and the tests will then complete normally. This is enough to make me feel strongly that this is related to Bug 44344. Check out that bug for a more verbose description of where things might be going wrong. Basically, I think some pieces of either GTK or SWT don't deal very well with the possibility of the X Windows session having serviced a request for XGrabPointer or XGrabKeyboard.
Moving since Felipe has bug 44344.
Does this still happen ? I think SSQ changes for Clipboard and Shell#setVisible() got this problem fixed. Please, retry. let me know if this is fixed.
I'm not sure that Silenio's fix had anything to do with this though, as I haven't seen this in quite a while. But it does appear to be fixed.
closing