Home » Archived » Test and Performance Tools Platform (TPTP) » No more handles during startup of AGR test on Linux
No more handles during startup of AGR test on Linux [message #86846] |
Sat, 11 November 2006 18:22 |
|
This is a multi-part message in MIME format.
--------------000904070006060904040902
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hi,
I am trying to get our test suites running under Linux. Since I am
running RH Linux ES version 4 EM64T which is problematic for TPTP
because the Agent Controller has not been ported yet, I have installed
jdk-1_5_0_09-linux-i586 and eclipse-platform-3.2.1-linux-gtk, both 32
bit implementations. On top of this I have installed the latest Callisto
and org.eclipse.tptp.test.auto-TPTP-4.2.1. Everything appears to
function properly until I attempt to run a test. Even a very basic newly
recorded test that simply launches a workspace and creates a new project
fails. The symptoms are that the test stalls at 60% and the eclipse
never launches. Once I cancel it the log contains the following output.
I understand the meaning running out of handles and the usual cause of
not releasing resources. Since in the this case the Eclipse never gets
on shown I scratch my head at exactly what resource can be exhausted yet.
Thanks for your thoughts,
Joel
eclipse.buildId=M20060921-0945
java.version=1.5.0_09
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -data
/home/joel/projects/Etish-32/../auto-gui-workspace
!ENTRY org.eclipse.osgi 4 0 2006-11-11 11:55:14.099
!MESSAGE Application error
!STACK 1
org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
at org.eclipse.swt.SWT.error(SWT.java:3400)
at org.eclipse.swt.widgets.Display.createDisplay(Display.java:7 93)
at org.eclipse.swt.widgets.Display.create(Display.java:781)
at org.eclipse.swt.graphics.Device.<init>(Device.java:145)
at org.eclipse.swt.widgets.Display.<init>(Display.java:452)
at org.eclipse.swt.widgets.Display.<init>(Display.java:443)
at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.ja va:448)
at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161)
at
org.eclipse.ui.internal.ide.IDEApplication.createDisplay(IDE Application.java:122)
at
org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:75)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:78)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:92)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:68)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:400)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)
--------------000904070006060904040902
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Helvetica, Arial, sans-serif">Hi,<br>
<br>
I am trying to get our test suites running under Linux. Since I am
running RH Linux ES version 4 EM64T which is problematic for TPTP
because the Agent Controller has not been ported yet, I have installed <font
color="#993399">jdk-1_5_0_09-linux-i586</font> and <font
color="#993399">eclipse-platform-3.2.1-linux-gtk</font>, both 32 bit
implementations. On top of this I have installed the latest Callisto
and <font color="#993399">org.eclipse.tptp.test.auto-TPTP-4.2.1</font >.
Everything appears to function properly until I attempt to run a test.
Even a very basic newly recorded test that simply launches a workspace
and creates a new project fails. The symptoms are that the test stalls
at 60% and the eclipse never launches. Once I cancel it the log
contains the following output. I understand the meaning running out of
handles and the usual cause of not releasing resources. Since in the
this case the Eclipse never gets on shown I scratch my head at exactly
what resource can be exhausted yet.<br>
<br>
Thanks for your thoughts,<br>
Joel<br>
</font><font face="Helvetica, Arial, sans-serif"><br>
</font>
<blockquote><tt>eclipse.buildId=M20060921-0945</tt><br>
<tt>java.version=1.5.0_09</tt><br>
<tt>java.vendor=Sun Microsystems Inc.</tt><br>
<tt>BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US</tt><br>
<tt>Command-line arguments: -data
/home/joel/projects/Etish-32/../auto-gui-workspace</tt><br >
<br>
<tt>!ENTRY org.eclipse.osgi 4 0 2006-11-11 11:55:14.099</tt><br>
<tt>!MESSAGE Application error</tt><br>
<tt>!STACK 1</tt><br>
<tt>org.eclipse.swt.SWTError: No more handles [gtk_init_check()
failed]</tt><br>
<tt> at org.eclipse.swt.SWT.error(SWT.java:3400)</tt><br>
<tt> at
org.eclipse.swt.widgets.Display.createDisplay(Display.java:7 93) </tt><br>
<tt> at org.eclipse.swt.widgets.Display.create(Display.java:781)</tt ><br>
<tt> at org.eclipse.swt.graphics.Device.<init>(Device. java:145) </tt><br>
<tt> at
org.eclipse.swt.widgets.Display.<init>(Display .java:452) </tt><br>
<tt> at
org.eclipse.swt.widgets.Display.<init>(Display .java:443) </tt><br>
<tt> at
org.eclipse.ui.internal.Workbench.createDisplay(Workbench.ja va:448) </tt><br>
<tt> at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161) </tt><br>
<tt> at
org.eclipse.ui.internal.ide.IDEApplication.createDisplay(IDE Application.java:122) </tt><br>
<tt> at
org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:75) </tt><br>
<tt> at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:78) </tt><br>
<tt> at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:92) </tt><br>
<tt> at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:68) </tt><br>
<tt> at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:400) </tt><br>
<tt> at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:177) </tt><br>
<tt> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)</tt><br>
<tt> at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39) </tt><br>
<tt> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25) </tt><br>
<tt> at java.lang.reflect.Method.invoke(Method.java:585)</tt><br>
<tt> at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 ) </tt><br>
<tt> at org.eclipse.core.launcher.Main.basicRun(Main.java:280)</tt> <br>
<tt> at org.eclipse.core.launcher.Main.run(Main.java:977)</tt><br>
<tt> at org.eclipse.core.launcher.Main.main(Main.java:952)</tt><br >
</blockquote>
<font face="Helvetica, Arial, sans-serif"><br>
<br>
<br>
</font>
</body>
</html>
--------------000904070006060904040902--
|
|
|
Re: No more handles during startup of AGR test on Linux [message #87169 is a reply to message #86846] |
Tue, 14 November 2006 19:55 |
|
This is a multi-part message in MIME format.
--------------020408080509080809010507
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hi,
Sorry for the cross post, but it appears from the silence that perhaps I
chose the wrong newsgroup for my query.
Thanks,
Joel
Joel Rosi-Schwartz wrote:
> Hi,
>
> I am trying to get our test suites running under Linux. Since I am
> running RH Linux ES version 4 EM64T which is problematic for TPTP
> because the Agent Controller has not been ported yet, I have installed
> jdk-1_5_0_09-linux-i586 and eclipse-platform-3.2.1-linux-gtk, both 32
> bit implementations. On top of this I have installed the latest
> Callisto and org.eclipse.tptp.test.auto-TPTP-4.2.1. Everything
> appears to function properly until I attempt to run a test. Even a
> very basic newly recorded test that simply launches a workspace and
> creates a new project fails. The symptoms are that the test stalls at
> 60% and the eclipse never launches. Once I cancel it the log contains
> the following output. I understand the meaning running out of handles
> and the usual cause of not releasing resources. Since in the this case
> the Eclipse never gets on shown I scratch my head at exactly what
> resource can be exhausted yet.
>
> Thanks for your thoughts,
> Joel
>
> eclipse.buildId=M20060921-0945
> java.version=1.5.0_09
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
> Command-line arguments: -data
> /home/joel/projects/Etish-32/../auto-gui-workspace
>
> !ENTRY org.eclipse.osgi 4 0 2006-11-11 11:55:14.099
> !MESSAGE Application error
> !STACK 1
> org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
> at org.eclipse.swt.SWT.error(SWT.java:3400)
> at org.eclipse.swt.widgets.Display.createDisplay(Display.java:7 93)
> at org.eclipse.swt.widgets.Display.create(Display.java:781)
> at org.eclipse.swt.graphics.Device.<init>(Device.java:145)
> at org.eclipse.swt.widgets.Display.<init>(Display.java:452)
> at org.eclipse.swt.widgets.Display.<init>(Display.java:443)
> at
> org.eclipse.ui.internal.Workbench.createDisplay(Workbench.ja va:448)
> at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161)
> at
> org.eclipse.ui.internal.ide.IDEApplication.createDisplay(IDE Application.java:122)
> at
> org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:75)
> at
> org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:78)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:92)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:68)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:400)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:177)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 )
> at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
> at org.eclipse.core.launcher.Main.run(Main.java:977)
> at org.eclipse.core.launcher.Main.main(Main.java:952)
>
>
>
>
--------------020408080509080809010507
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Helvetica, Arial, sans-serif">Hi,<br>
<br>
Sorry for the cross post, but it appears from the silence that perhaps
I chose the wrong newsgroup for my query.<br>
<br>
Thanks,<br>
Joel<br>
</font><br>
Joel Rosi-Schwartz wrote:
<blockquote cite="midej54dc$umo$1@utils.eclipse.org" type="cite">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<font face="Helvetica, Arial, sans-serif">Hi,<br>
<br>
I am trying to get our test suites running under Linux. Since I am
running RH Linux ES version 4 EM64T which is problematic for TPTP
because the Agent Controller has not been ported yet, I have installed <font
color="#993399">jdk-1_5_0_09-linux-i586</font> and <font
color="#993399">eclipse-platform-3.2.1-linux-gtk</font>, both 32 bit
implementations. On top of this I have installed the latest Callisto
and <font color="#993399">org.eclipse.tptp.test.auto-TPTP-4.2.1</font >.
Everything appears to function properly until I attempt to run a test.
Even a very basic newly recorded test that simply launches a workspace
and creates a new project fails. The symptoms are that the test stalls
at 60% and the eclipse never launches. Once I cancel it the log
contains the following output. I understand the meaning running out of
handles and the usual cause of not releasing resources. Since in the
this case the Eclipse never gets on shown I scratch my head at exactly
what resource can be exhausted yet.<br>
<br>
Thanks for your thoughts,<br>
Joel<br>
</font><font face="Helvetica, Arial, sans-serif"><br>
</font>
<blockquote><tt>eclipse.buildId=M20060921-0945</tt><br>
<tt>java.version=1.5.0_09</tt><br>
<tt>java.vendor=Sun Microsystems Inc.</tt><br>
<tt>BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US</tt><br>
<tt>Command-line arguments: -data
/home/joel/projects/Etish-32/../auto-gui-workspace</tt><br >
<br>
<tt>!ENTRY org.eclipse.osgi 4 0 2006-11-11 11:55:14.099</tt><br>
<tt>!MESSAGE Application error</tt><br>
<tt>!STACK 1</tt><br>
<tt>org.eclipse.swt.SWTError: No more handles [gtk_init_check()
failed]</tt><br>
<tt> at org.eclipse.swt.SWT.error(SWT.java:3400)</tt><br>
<tt> at
org.eclipse.swt.widgets.Display.createDisplay(Display.java:7 93) </tt><br>
<tt> at org.eclipse.swt.widgets.Display.create(Display.java:781)</tt ><br>
<tt> at
org.eclipse.swt.graphics.Device.<init>(Device. java:145) </tt><br>
<tt> at
org.eclipse.swt.widgets.Display.<init>(Display .java:452) </tt><br>
<tt> at
org.eclipse.swt.widgets.Display.<init>(Display .java:443) </tt><br>
<tt> at
org.eclipse.ui.internal.Workbench.createDisplay(Workbench.ja va:448) </tt><br>
<tt> at
org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161) </tt><br>
<tt> at
org.eclipse.ui.internal.ide.IDEApplication.createDisplay(IDE Application.java:122) </tt><br>
<tt> at
org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:75) </tt><br>
<tt> at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:78) </tt><br>
<tt> at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:92) </tt><br>
<tt> at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:68) </tt><br>
<tt> at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:400) </tt><br>
<tt> at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:177) </tt><br>
<tt> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)</tt><br>
<tt> at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39) </tt><br>
<tt> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25) </tt><br>
<tt> at java.lang.reflect.Method.invoke(Method.java:585)</tt><br>
<tt> at
org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 ) </tt><br>
<tt> at org.eclipse.core.launcher.Main.basicRun(Main.java:280)</tt> <br>
<tt> at org.eclipse.core.launcher.Main.run(Main.java:977)</tt><br>
<tt> at org.eclipse.core.launcher.Main.main(Main.java:952)</tt><br >
</blockquote>
<font face="Helvetica, Arial, sans-serif"><br>
<br>
<br>
</font>
</blockquote>
</body>
</html>
--------------020408080509080809010507--
|
|
|
Re: No more handles during startup of AGR test on Linux [message #87354 is a reply to message #87169] |
Wed, 15 November 2006 12:17 |
Eclipse User |
|
|
|
Originally posted by: ffr.softwareag.com
No, you're right here I think because I have the same problem.
Does your test make extensive use of (context-) menus of the application
(i.e. Plug-in) under test in your test scenario? What I found out is that
AGR requires menus from the application under test but never disposes them.
After applying a little code to BooleanSelectionCommand
(package=org.eclipse.tptp.test.auto.gui.internal.commands) things go much
better for me but are not perfect. The handle count still increases during
test execution. It is very hard to find out all the places where the runner
allocates resources without disposing them. I'll create a bugzilla entry for
this.
"Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org> wrote in message
news:ejd700$ib6$2@utils.eclipse.org...
> Hi,
>
> Sorry for the cross post, but it appears from the silence that perhaps I
> chose the wrong newsgroup for my query.
>
> Thanks,
> Joel
>
> Joel Rosi-Schwartz wrote:
>> Hi,
>>
>> I am trying to get our test suites running under Linux. Since I am
>> running RH Linux ES version 4 EM64T which is problematic for TPTP
>> because the Agent Controller has not been ported yet, I have installed
>> jdk-1_5_0_09-linux-i586 and eclipse-platform-3.2.1-linux-gtk, both 32
>> bit implementations. On top of this I have installed the latest
>> Callisto and org.eclipse.tptp.test.auto-TPTP-4.2.1. Everything
>> appears to function properly until I attempt to run a test. Even a
>> very basic newly recorded test that simply launches a workspace and
>> creates a new project fails. The symptoms are that the test stalls at
>> 60% and the eclipse never launches. Once I cancel it the log contains
>> the following output. I understand the meaning running out of handles
>> and the usual cause of not releasing resources. Since in the this case
>> the Eclipse never gets on shown I scratch my head at exactly what
>> resource can be exhausted yet.
>>
>> Thanks for your thoughts,
>> Joel
>>
>> eclipse.buildId=M20060921-0945
>> java.version=1.5.0_09
>> java.vendor=Sun Microsystems Inc.
>> BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
>> Command-line arguments: -data
>> /home/joel/projects/Etish-32/../auto-gui-workspace
>>
>> !ENTRY org.eclipse.osgi 4 0 2006-11-11 11:55:14.099
>> !MESSAGE Application error
>> !STACK 1
>> org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
>> at org.eclipse.swt.SWT.error(SWT.java:3400)
>> at org.eclipse.swt.widgets.Display.createDisplay(Display.java:7 93)
>> at org.eclipse.swt.widgets.Display.create(Display.java:781)
>> at org.eclipse.swt.graphics.Device.<init>(Device.java:145)
>> at org.eclipse.swt.widgets.Display.<init>(Display.java:452)
>> at org.eclipse.swt.widgets.Display.<init>(Display.java:443)
>> at
>> org.eclipse.ui.internal.Workbench.createDisplay(Workbench.ja va:448)
>> at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161)
>> at
>>
>> org.eclipse.ui.internal.ide.IDEApplication.createDisplay(IDE Application.java:122)
>> at
>>
>> org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:75)
>> at
>>
>> org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:78)
>> at
>>
>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:92)
>> at
>>
>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:68)
>> at
>>
>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:400)
>> at
>>
>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:177)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>> at
>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:585)
>> at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 )
>> at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
>> at org.eclipse.core.launcher.Main.run(Main.java:977)
>> at org.eclipse.core.launcher.Main.main(Main.java:952)
>>
>>
>>
>>
>
|
|
|
Re: No more handles during startup of AGR test on Linux [message #87401 is a reply to message #87354] |
Wed, 15 November 2006 13:52 |
Eclipse User |
|
|
|
Originally posted by: ffr.softwareag.com
Stop, I'm wrong! It is our application which dynamically creates menus! Two
requests, two menus even if they look identically. The menus need to be
disposed from within the application. In fact, AGR must not dispose
application menus. Hope, I didn't confuse anyone.
"Frank Froehlich" <ffr@softwareag.com> wrote in message
news:ejf0g1$cha$1@utils.eclipse.org...
> No, you're right here I think because I have the same problem.
>
> Does your test make extensive use of (context-) menus of the application
> (i.e. Plug-in) under test in your test scenario? What I found out is that
> AGR requires menus from the application under test but never disposes
> them. After applying a little code to BooleanSelectionCommand
> (package=org.eclipse.tptp.test.auto.gui.internal.commands) things go much
> better for me but are not perfect. The handle count still increases during
> test execution. It is very hard to find out all the places where the
> runner allocates resources without disposing them. I'll create a bugzilla
> entry for this.
>
>
> "Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org> wrote in message
> news:ejd700$ib6$2@utils.eclipse.org...
>> Hi,
>>
>> Sorry for the cross post, but it appears from the silence that perhaps I
>> chose the wrong newsgroup for my query.
>>
>> Thanks,
>> Joel
>>
>> Joel Rosi-Schwartz wrote:
>>> Hi,
>>>
>>> I am trying to get our test suites running under Linux. Since I am
>>> running RH Linux ES version 4 EM64T which is problematic for TPTP
>>> because the Agent Controller has not been ported yet, I have installed
>>> jdk-1_5_0_09-linux-i586 and eclipse-platform-3.2.1-linux-gtk, both 32
>>> bit implementations. On top of this I have installed the latest
>>> Callisto and org.eclipse.tptp.test.auto-TPTP-4.2.1. Everything
>>> appears to function properly until I attempt to run a test. Even a
>>> very basic newly recorded test that simply launches a workspace and
>>> creates a new project fails. The symptoms are that the test stalls at
>>> 60% and the eclipse never launches. Once I cancel it the log contains
>>> the following output. I understand the meaning running out of handles
>>> and the usual cause of not releasing resources. Since in the this case
>>> the Eclipse never gets on shown I scratch my head at exactly what
>>> resource can be exhausted yet.
>>>
>>> Thanks for your thoughts,
>>> Joel
>>>
>>> eclipse.buildId=M20060921-0945
>>> java.version=1.5.0_09
>>> java.vendor=Sun Microsystems Inc.
>>> BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
>>> Command-line arguments: -data
>>> /home/joel/projects/Etish-32/../auto-gui-workspace
>>>
>>> !ENTRY org.eclipse.osgi 4 0 2006-11-11 11:55:14.099
>>> !MESSAGE Application error
>>> !STACK 1
>>> org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
>>> at org.eclipse.swt.SWT.error(SWT.java:3400)
>>> at org.eclipse.swt.widgets.Display.createDisplay(Display.java:7 93)
>>> at org.eclipse.swt.widgets.Display.create(Display.java:781)
>>> at org.eclipse.swt.graphics.Device.<init>(Device.java:145)
>>> at org.eclipse.swt.widgets.Display.<init>(Display.java:452)
>>> at org.eclipse.swt.widgets.Display.<init>(Display.java:443)
>>> at
>>> org.eclipse.ui.internal.Workbench.createDisplay(Workbench.ja va:448)
>>> at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161)
>>> at
>>>
>>> org.eclipse.ui.internal.ide.IDEApplication.createDisplay(IDE Application.java:122)
>>> at
>>>
>>> org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:75)
>>> at
>>>
>>> org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:78)
>>> at
>>>
>>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:92)
>>> at
>>>
>>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:68)
>>> at
>>>
>>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:400)
>>> at
>>>
>>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:177)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>>
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>> at
>>>
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:585)
>>> at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 )
>>> at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
>>> at org.eclipse.core.launcher.Main.run(Main.java:977)
>>> at org.eclipse.core.launcher.Main.main(Main.java:952)
>>>
>>>
>>>
>>>
>>
>
>
|
|
| |
Re: No more handles during startup of AGR test on Linux [message #87471 is a reply to message #87169] |
Wed, 15 November 2006 19:31 |
Grant Gayed Messages: 2150 Registered: July 2009 |
Senior Member |
|
|
Hi Joel,
This indicates that the display could not be created. This sometimes (but
not always) occurs as a result of the DISPLAY environment variable not being
set.
The following link queries eclipse's bugzilla for gtk_init_check:
https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advan ced&short_desc_type=allwordssubstr&short_desc=&l ong_desc_type=allwordssubstr&long_desc=gtk_init_check&am p;bug_file_loc_type=allwordssubstr&bug_file_loc=&sta tus_whiteboard_type=allwordssubstr&status_whiteboard=&am p;keywords_type=allwords&keywords=&emailtype1=substr ing&email1=&emailtype2=substring&email2=&bug idtype=include&bug_id=&votes=&chfieldfrom=&c hfieldto=Now&chfieldvalue=&cmdtype=doit&order=Re use+same+sort+as+last+time&field0-0-0=noop&type0-0-0 =noop&value0-0-0= .
There are some reports here that are probably relevant to your context, and
in particular https://bugs.eclipse.org/bugs/show_bug.cgi?id=106396 has a lot
of info.
Grant
"Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org> wrote in message
news:ejd700$ib6$2@utils.eclipse.org...
Hi,
Sorry for the cross post, but it appears from the silence that perhaps I
chose the wrong newsgroup for my query.
Thanks,
Joel
Joel Rosi-Schwartz wrote:
Hi,
I am trying to get our test suites running under Linux. Since I am running
RH Linux ES version 4 EM64T which is problematic for TPTP because the Agent
Controller has not been ported yet, I have installed jdk-1_5_0_09-linux-i586
and eclipse-platform-3.2.1-linux-gtk, both 32 bit implementations. On top of
this I have installed the latest Callisto and
org.eclipse.tptp.test.auto-TPTP-4.2.1. Everything appears to function
properly until I attempt to run a test. Even a very basic newly recorded
test that simply launches a workspace and creates a new project fails. The
symptoms are that the test stalls at 60% and the eclipse never launches.
Once I cancel it the log contains the following output. I understand the
meaning running out of handles and the usual cause of not releasing
resources. Since in the this case the Eclipse never gets on shown I scratch
my head at exactly what resource can be exhausted yet.
Thanks for your thoughts,
Joel
eclipse.buildId=M20060921-0945
java.version=1.5.0_09
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -data
/home/joel/projects/Etish-32/../auto-gui-workspace
!ENTRY org.eclipse.osgi 4 0 2006-11-11 11:55:14.099
!MESSAGE Application error
!STACK 1
org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
at org.eclipse.swt.SWT.error(SWT.java:3400)
at org.eclipse.swt.widgets.Display.createDisplay(Display.java:7 93)
at org.eclipse.swt.widgets.Display.create(Display.java:781)
at org.eclipse.swt.graphics.Device.<init>(Device.java:145)
at org.eclipse.swt.widgets.Display.<init>(Display.java:452)
at org.eclipse.swt.widgets.Display.<init>(Display.java:443)
at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.ja va:448)
at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161)
at
org.eclipse.ui.internal.ide.IDEApplication.createDisplay(IDE Application.java
:122)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:75)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.
java:78)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(
EclipseAppLauncher.java:92)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAp
pLauncher.java:68)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:400)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl
..java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)
|
|
|
Re: No more handles during startup of AGR test on Linux [message #87486 is a reply to message #86846] |
Wed, 15 November 2006 20:30 |
Eclipse User |
|
|
|
Originally posted by: ffr.softwareag.com
Not exactly suitable for this entry, please keep this just for your
information therefore: Every invocation of the AdaptiveWidgetResolver during
playback leads to consumption of a file handle which is not freed until test
execution finishes. I created a bugzilla entry for this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=164702
"Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org> wrote in message
news:ej54dc$umo$1@utils.eclipse.org...
> Hi,
>
> I am trying to get our test suites running under Linux. Since I am
> running RH Linux ES version 4 EM64T which is problematic for TPTP
> because the Agent Controller has not been ported yet, I have installed
> jdk-1_5_0_09-linux-i586 and eclipse-platform-3.2.1-linux-gtk, both 32
> bit implementations. On top of this I have installed the latest Callisto
> and org.eclipse.tptp.test.auto-TPTP-4.2.1. Everything appears to
> function properly until I attempt to run a test. Even a very basic newly
> recorded test that simply launches a workspace and creates a new project
> fails. The symptoms are that the test stalls at 60% and the eclipse
> never launches. Once I cancel it the log contains the following output.
> I understand the meaning running out of handles and the usual cause of
> not releasing resources. Since in the this case the Eclipse never gets
> on shown I scratch my head at exactly what resource can be exhausted yet.
>
> Thanks for your thoughts,
> Joel
>
> eclipse.buildId=M20060921-0945
> java.version=1.5.0_09
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
> Command-line arguments: -data
> /home/joel/projects/Etish-32/../auto-gui-workspace
>
> !ENTRY org.eclipse.osgi 4 0 2006-11-11 11:55:14.099
> !MESSAGE Application error
> !STACK 1
> org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
> at org.eclipse.swt.SWT.error(SWT.java:3400)
> at org.eclipse.swt.widgets.Display.createDisplay(Display.java:7 93)
> at org.eclipse.swt.widgets.Display.create(Display.java:781)
> at org.eclipse.swt.graphics.Device.<init>(Device.java:145)
> at org.eclipse.swt.widgets.Display.<init>(Display.java:452)
> at org.eclipse.swt.widgets.Display.<init>(Display.java:443)
> at
> org.eclipse.ui.internal.Workbench.createDisplay(Workbench.ja va:448)
> at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161)
> at
>
> org.eclipse.ui.internal.ide.IDEApplication.createDisplay(IDE Application.java:122)
> at
> org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:75)
> at
>
> org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:78)
> at
>
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:92)
> at
>
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:68)
> at
>
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:400)
> at
>
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:177)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
> at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 )
> at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
> at org.eclipse.core.launcher.Main.run(Main.java:977)
> at org.eclipse.core.launcher.Main.main(Main.java:952)
>
>
>
>
>
|
|
|
Re: No more handles during startup of AGR test on Linux [message #87536 is a reply to message #86846] |
Wed, 15 November 2006 23:59 |
No real name Messages: 404 Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0071_01C708E8.31E11D20
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi Joel,
Please see https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D115648 to see =
if any of the workarounds suggested will help.
Thanks,
Ali Mehregani
"Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org> wrote in message =
news:ej54dc$umo$1@utils.eclipse.org...
Hi,
I am trying to get our test suites running under Linux. Since I am =
running RH Linux ES version 4 EM64T which is problematic for TPTP =
because the Agent Controller has not been ported yet, I have installed =
jdk-1_5_0_09-linux-i586 and eclipse-platform-3.2.1-linux-gtk, both 32 =
bit implementations. On top of this I have installed the latest Callisto =
and org.eclipse.tptp.test.auto-TPTP-4.2.1. Everything appears to =
function properly until I attempt to run a test. Even a very basic newly =
recorded test that simply launches a workspace and creates a new project =
fails. The symptoms are that the test stalls at 60% and the eclipse =
never launches. Once I cancel it the log contains the following output. =
I understand the meaning running out of handles and the usual cause of =
not releasing resources. Since in the this case the Eclipse never gets =
on shown I scratch my head at exactly what resource can be exhausted =
yet.
Thanks for your thoughts,
Joel
eclipse.buildId=3DM20060921-0945
java.version=3D1.5.0_09
java.vendor=3DSun Microsystems Inc.
BootLoader constants: OS=3Dlinux, ARCH=3Dx86, WS=3Dgtk, NL=3Den_US
Command-line arguments: -data =
/home/joel/projects/Etish-32/../auto-gui-workspace
!ENTRY org.eclipse.osgi 4 0 2006-11-11 11:55:14.099
!MESSAGE Application error
!STACK 1
org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
at org.eclipse.swt.SWT.error(SWT.java:3400)
at org.eclipse.swt.widgets.Display.createDisplay(Display.java:7 93)
at org.eclipse.swt.widgets.Display.create(Display.java:781)
at org.eclipse.swt.graphics.Device.<init>(Device.java:145)
at org.eclipse.swt.widgets.Display.<init>(Display.java:452)
at org.eclipse.swt.widgets.Display.<init>(Display.java:443)
at =
org.eclipse.ui.internal.Workbench.createDisplay(Workbench.ja va:448)
at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161)
at =
org.eclipse.ui.internal.ide.IDEApplication.createDisplay(IDE Application.j=
ava:122)
at =
org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:75)
at =
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivat=
or.java:78)
at =
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplicati=
on(EclipseAppLauncher.java:92)
at =
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(Eclips=
eAppLauncher.java:68)
at =
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:4=
00)
at =
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:1=
77)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at =
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java=
:39)
at =
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorI=
mpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)
------=_NextPart_000_0071_01C708E8.31E11D20
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type =
content=3Dtext/html;charset=3DISO-8859-1>
<META content=3D"MSHTML 6.00.2900.2963" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi Joel,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Please see <A=20
href=3D"https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D115648">https://b=
ugs.eclipse.org/bugs/show_bug.cgi?id=3D115648</A> to=20
see if any of the workarounds suggested will help.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Thanks,</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Ali Mehregani</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Joel Rosi-Schwartz" <<A=20
=
href=3D"mailto:Joel.Rosi-Schwartz@Etish.org">Joel.Rosi-Schwartz@Etish.org=
</A>>=20
wrote in message <A=20
=
href=3D"news:ej54dc$umo$1@utils.eclipse.org">news:ej54dc$umo$1@utils.ecli=
pse.org</A>...</DIV><FONT=20
face=3D"Helvetica, Arial, sans-serif">Hi,<BR><BR>I am trying to get =
our test=20
suites running under Linux. Since I am running RH Linux ES version 4 =
EM64T=20
which is problematic for TPTP because the Agent Controller has not =
been ported=20
yet, I have installed <FONT =
color=3D#993399>jdk-1_5_0_09-linux-i586</FONT> and=20
<FONT color=3D#993399>eclipse-platform-3.2.1-linux-gtk</FONT>, both 32 =
bit=20
implementations. On top of this I have installed the latest Callisto =
and <FONT=20
color=3D#993399>org.eclipse.tptp.test.auto-TPTP-4.2.1</FONT >. =
Everything=20
appears to function properly until I attempt to run a test. Even a =
very basic=20
newly recorded test that simply launches a workspace and creates a new =
project=20
fails. The symptoms are that the test stalls at 60% and the eclipse =
never=20
launches. Once I cancel it the log contains the following output. I =
understand=20
the meaning running out of handles and the usual cause of not =
releasing=20
resources. Since in the this case the Eclipse never gets on shown I =
scratch my=20
head at exactly what resource can be exhausted yet.<BR><BR>Thanks for =
your=20
thoughts,<BR>Joel<BR></FONT><FONT=20
face=3D"Helvetica, Arial, sans-serif"><BR></FONT>
=
<BLOCKQUOTE><TT>eclipse.buildId=3DM20060921-0945</TT><BR ><TT>java.version=
=3D1.5.0_09</TT><BR><TT>java.vendor=3DSun=20
Microsystems Inc.</TT><BR><TT>BootLoader constants: OS=3Dlinux, =
ARCH=3Dx86,=20
WS=3Dgtk, NL=3Den_US</TT><BR><TT>Command-line arguments: -data =
=
/home/joel/projects/Etish-32/../auto-gui-workspace</TT><BR ><BR><TT>!ENTRY=
=20
org.eclipse.osgi 4 0 2006-11-11 11:55:14.099</TT><BR><TT>!MESSAGE=20
Application error</TT><BR><TT>!STACK =
1</TT><BR><TT>org.eclipse.swt.SWTError:=20
No more handles [gtk_init_check() failed]</TT><BR><TT> at=20
org.eclipse.swt.SWT.error(SWT.java:3400)</TT><BR><TT> at=20
=
org.eclipse.swt.widgets.Display.createDisplay(Display.java:7 93) </TT><BR><=
TT> =20
at=20
=
org.eclipse.swt.widgets.Display.create(Display.java:781)</TT ><BR><TT>&nbs=
p;=20
at=20
=
org.eclipse.swt.graphics.Device.<init>(Device. java:145) </TT><BR><TT=
> =20
at=20
=
org.eclipse.swt.widgets.Display.<init>(Display .java:452) </TT><BR><T=
T> =20
at=20
=
org.eclipse.swt.widgets.Display.<init>(Display .java:443) </TT><BR><T=
T> =20
at=20
=
org.eclipse.ui.internal.Workbench.createDisplay(Workbench.ja va:448) </TT><=
BR><TT> =20
at=20
=
org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161) </TT><BR><TT>=
=20
at=20
=
org.eclipse.ui.internal.ide.IDEApplication.createDisplay(IDE Application.j=
ava:122)</TT><BR><TT> =20
at=20
=
org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:75) </T=
T><BR><TT> =20
at=20
=
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivat=
or.java:78)</TT><BR><TT> =20
at=20
=
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplicati=
on(EclipseAppLauncher.java:92)</TT><BR><TT> =20
at=20
=
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(Eclips=
eAppLauncher.java:68)</TT><BR><TT> =20
at=20
=
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:4=
00)</TT><BR><TT> =20
at=20
=
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:1=
77)</TT><BR><TT> =20
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native=20
Method)</TT><BR><TT> at=20
=
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java=
:39)</TT><BR><TT> =20
at=20
=
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorI=
mpl.java:25)</TT><BR><TT> =20
at =
java.lang.reflect.Method.invoke(Method.java:585)</TT><BR><TT > at=20
=
org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 ) </TT><BR><TT=
> =20
at =
org.eclipse.core.launcher.Main.basicRun(Main.java:280)</TT> <BR><TT> =
=20
at =
org.eclipse.core.launcher.Main.run(Main.java:977)</TT><BR> <TT> at=20
=
org.eclipse.core.launcher.Main.main(Main.java:952)</TT><BR ></BLOCKQUOTE><=
FONT=20
face=3D"Helvetica, Arial, =
sans-serif"><BR><BR><BR></BLOCKQUOTE></FONT></BODY></HTML >
------=_NextPart_000_0071_01C708E8.31E11D20--
|
|
|
Re: No more handles during startup of AGR test on Linux [message #87551 is a reply to message #87486] |
Thu, 16 November 2006 00:00 |
No real name Messages: 404 Registered: July 2009 |
Senior Member |
|
|
A patch is attached to the defect.
It will be checked in as soon as CVS opens for 4.4 development.
Thanks,
Ali Mehregani
"Frank Froehlich" <ffr@softwareag.com> wrote in message
news:ejftdb$ugf$1@utils.eclipse.org...
> Not exactly suitable for this entry, please keep this just for your
> information therefore: Every invocation of the AdaptiveWidgetResolver
> during playback leads to consumption of a file handle which is not freed
> until test execution finishes. I created a bugzilla entry for this:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=164702
>
> "Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org> wrote in message
> news:ej54dc$umo$1@utils.eclipse.org...
>> Hi,
>>
>> I am trying to get our test suites running under Linux. Since I am
>> running RH Linux ES version 4 EM64T which is problematic for TPTP
>> because the Agent Controller has not been ported yet, I have installed
>> jdk-1_5_0_09-linux-i586 and eclipse-platform-3.2.1-linux-gtk, both 32
>> bit implementations. On top of this I have installed the latest Callisto
>> and org.eclipse.tptp.test.auto-TPTP-4.2.1. Everything appears to
>> function properly until I attempt to run a test. Even a very basic newly
>> recorded test that simply launches a workspace and creates a new project
>> fails. The symptoms are that the test stalls at 60% and the eclipse
>> never launches. Once I cancel it the log contains the following output.
>> I understand the meaning running out of handles and the usual cause of
>> not releasing resources. Since in the this case the Eclipse never gets
>> on shown I scratch my head at exactly what resource can be exhausted yet.
>>
>> Thanks for your thoughts,
>> Joel
>>
>> eclipse.buildId=M20060921-0945
>> java.version=1.5.0_09
>> java.vendor=Sun Microsystems Inc.
>> BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
>> Command-line arguments: -data
>> /home/joel/projects/Etish-32/../auto-gui-workspace
>>
>> !ENTRY org.eclipse.osgi 4 0 2006-11-11 11:55:14.099
>> !MESSAGE Application error
>> !STACK 1
>> org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
>> at org.eclipse.swt.SWT.error(SWT.java:3400)
>> at org.eclipse.swt.widgets.Display.createDisplay(Display.java:7 93)
>> at org.eclipse.swt.widgets.Display.create(Display.java:781)
>> at org.eclipse.swt.graphics.Device.<init>(Device.java:145)
>> at org.eclipse.swt.widgets.Display.<init>(Display.java:452)
>> at org.eclipse.swt.widgets.Display.<init>(Display.java:443)
>> at
>> org.eclipse.ui.internal.Workbench.createDisplay(Workbench.ja va:448)
>> at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161)
>> at
>>
>> org.eclipse.ui.internal.ide.IDEApplication.createDisplay(IDE Application.java:122)
>> at
>> org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:75)
>> at
>>
>> org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:78)
>> at
>>
>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:92)
>> at
>>
>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:68)
>> at
>>
>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:400)
>> at
>>
>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:177)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>> at
>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:585)
>> at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 )
>> at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
>> at org.eclipse.core.launcher.Main.run(Main.java:977)
>> at org.eclipse.core.launcher.Main.main(Main.java:952)
>>
>>
>>
>>
>>
>
>
|
|
| | | |
Re: No more handles during startup of AGR test on Linux [message #87934 is a reply to message #87536] |
Sun, 19 November 2006 17:15 |
|
This is a multi-part message in MIME format.
--------------030500020202000005020902
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hi Ali,
I have read through the various bug reports on this issue and have tried
various suggestions. So far I have made no progress with resolving it.
Considering that EM64T is an unsupported platform and that my attempts
to run in 32 bit mode is somewhat of an experiment, I have decide not to
pursue this issue further at the moment. Instead we will continue to use
XP as our primary development platform. I will set up a standalone 32
bit Linux on a spare machine and use it solely for testing our
application under Linux at each milestone. In the future when EM64T is
officially supported we will take another shot a moving our development
platform to Linux.
Thanks for your help on this and I am sorry that I was not able to add
much to the knowledge base.
Joel
Ali Mehregani wrote:
> Hi Joel,
>
> Please see https://bugs.eclipse.org/bugs/show_bug.cgi?id=115648 to see
> if any of the workarounds suggested will help.
> Thanks,
>
> Ali Mehregani
>
> "Joel Rosi-Schwartz" <Joel.Rosi-Schwartz@Etish.org
> <mailto:Joel.Rosi-Schwartz@Etish.org>> wrote in message
> news:ej54dc$umo$1@utils.eclipse.org...
> Hi,
>
> I am trying to get our test suites running under Linux. Since I am
> running RH Linux ES version 4 EM64T which is problematic for TPTP
> because the Agent Controller has not been ported yet, I have
> installed jdk-1_5_0_09-linux-i586 and
> eclipse-platform-3.2.1-linux-gtk, both 32 bit implementations. On
> top of this I have installed the latest Callisto and
> org.eclipse.tptp.test.auto-TPTP-4.2.1. Everything appears to
> function properly until I attempt to run a test. Even a very basic
> newly recorded test that simply launches a workspace and creates a
> new project fails. The symptoms are that the test stalls at 60%
> and the eclipse never launches. Once I cancel it the log contains
> the following output. I understand the meaning running out of
> handles and the usual cause of not releasing resources. Since in
> the this case the Eclipse never gets on shown I scratch my head at
> exactly what resource can be exhausted yet.
>
> Thanks for your thoughts,
> Joel
>
> eclipse.buildId=M20060921-0945
> java.version=1.5.0_09
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
> Command-line arguments: -data
> /home/joel/projects/Etish-32/../auto-gui-workspace
>
> !ENTRY org.eclipse.osgi 4 0 2006-11-11 11:55:14.099
> !MESSAGE Application error
> !STACK 1
> org.eclipse.swt.SWTError: No more handles [gtk_init_check()
> failed]
> at org.eclipse.swt.SWT.error(SWT.java:3400)
> at
> org.eclipse.swt.widgets.Display.createDisplay(Display.java:7 93)
> at org.eclipse.swt.widgets.Display.create(Display.java:781)
> at org.eclipse.swt.graphics.Device.<init>(Device.java:145)
> at org.eclipse.swt.widgets.Display.<init>(Display.java:452)
> at org.eclipse.swt.widgets.Display.<init>(Display.java:443)
> at
> org.eclipse.ui.internal.Workbench.createDisplay(Workbench.ja va:448)
> at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161)
> at
> org.eclipse.ui.internal.ide.IDEApplication.createDisplay(IDE Application.java:122)
> at
> org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:75)
> at
> org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:78)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:92)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:68)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:400)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:177)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 )
> at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
> at org.eclipse.core.launcher.Main.run(Main.java:977)
> at org.eclipse.core.launcher.Main.main(Main.java:952)
>
>
>
>
--------------030500020202000005020902
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Helvetica, Arial, sans-serif">Hi Ali,<br>
<br>
I have read through the various bug reports on this issue and have
tried various suggestions. So far I have made no progress with
resolving it. Considering that EM64T is an unsupported platform and
that my attempts to run in 32 bit mode is somewhat of an experiment, I
have decide not to pursue this issue further at the moment. Instead we
will continue to use XP as our primary development platform. I will set
up a standalone 32 bit Linux on a spare machine and use it solely for
testing our application under Linux at each milestone. In the future
when EM64T is officially supported we will take another shot a moving
our development platform to Linux.<br>
<br>
Thanks for your help on this and I am sorry that I was not able to add
much to the knowledge base.<br>
<br>
Joel<br>
</font><br>
Ali Mehregani wrote:
<blockquote cite="midejg9ll$oab$1@utils.eclipse.org" type="cite">
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<meta content="MSHTML 6.00.2900.2963" name="GENERATOR">
<style></style>
<div><font face="Arial" size="2">Hi Joel,</font></div>
<div> </div>
<div><font face="Arial" size="2">Please see <a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=115648">https://bugs.eclipse.org/bugs/show_bug.cgi?id=115648</a> to
see if any of the workarounds suggested will help.</font></div>
<div><font face="Arial" size="2">Thanks,</font></div>
<div> </div>
<div><font face="Arial" size="2">Ali Mehregani</font></div>
<blockquote
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div>"Joel Rosi-Schwartz" <<a
href="mailto:Joel.Rosi-Schwartz@Etish.org">Joel.Rosi-Schwartz@Etish.org</a>>
wrote in message <a href="news:ej54dc$umo$1@utils.eclipse.org">news:ej54dc$umo$1@utils.eclipse.org</a>...</div>
<font face="Helvetica, Arial, sans-serif">Hi,<br>
<br>
I am trying to get our test suites running under Linux. Since I am
running RH Linux ES version 4 EM64T which is problematic for TPTP
because the Agent Controller has not been ported yet, I have installed <font
color="#993399">jdk-1_5_0_09-linux-i586</font> and <font
color="#993399">eclipse-platform-3.2.1-linux-gtk</font>, both 32 bit
implementations. On top of this I have installed the latest Callisto
and <font color="#993399">org.eclipse.tptp.test.auto-TPTP-4.2.1</font >.
Everything appears to function properly until I attempt to run a test.
Even a very basic newly recorded test that simply launches a workspace
and creates a new project fails. The symptoms are that the test stalls
at 60% and the eclipse never launches. Once I cancel it the log
contains the following output. I understand the meaning running out of
handles and the usual cause of not releasing resources. Since in the
this case the Eclipse never gets on shown I scratch my head at exactly
what resource can be exhausted yet.<br>
<br>
Thanks for your thoughts,<br>
Joel<br>
</font><font face="Helvetica, Arial, sans-serif"><br>
</font>
<blockquote><tt>eclipse.buildId=M20060921-0945</tt><br>
<tt>java.version=1.5.0_09</tt><br>
<tt>java.vendor=Sun Microsystems Inc.</tt><br>
<tt>BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US</tt><br>
<tt>Command-line arguments: -data
/home/joel/projects/Etish-32/../auto-gui-workspace</tt><br >
<br>
<tt>!ENTRY org.eclipse.osgi 4 0 2006-11-11 11:55:14.099</tt><br>
<tt>!MESSAGE Application error</tt><br>
<tt>!STACK 1</tt><br>
<tt>org.eclipse.swt.SWTError: No more handles [gtk_init_check()
failed]</tt><br>
<tt> at org.eclipse.swt.SWT.error(SWT.java:3400)</tt><br>
<tt> at
org.eclipse.swt.widgets.Display.createDisplay(Display.java:7 93) </tt><br>
<tt> at org.eclipse.swt.widgets.Display.create(Display.java:781)</tt ><br>
<tt> at
org.eclipse.swt.graphics.Device.<init>(Device. java:145) </tt><br>
<tt> at
org.eclipse.swt.widgets.Display.<init>(Display .java:452) </tt><br>
<tt> at
org.eclipse.swt.widgets.Display.<init>(Display .java:443) </tt><br>
<tt> at
org.eclipse.ui.internal.Workbench.createDisplay(Workbench.ja va:448) </tt><br>
<tt> at
org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161) </tt><br>
<tt> at
org.eclipse.ui.internal.ide.IDEApplication.createDisplay(IDE Application.java:122) </tt><br>
<tt> at
org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:75) </tt><br>
<tt> at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:78) </tt><br>
<tt> at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:92) </tt><br>
<tt> at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:68) </tt><br>
<tt> at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:400) </tt><br>
<tt> at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:177) </tt><br>
<tt> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)</tt><br>
<tt> at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39) </tt><br>
<tt> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25) </tt><br>
<tt> at java.lang.reflect.Method.invoke(Method.java:585)</tt><br>
<tt> at
org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 ) </tt><br>
<tt> at org.eclipse.core.launcher.Main.basicRun(Main.java:280)</tt> <br>
<tt> at org.eclipse.core.launcher.Main.run(Main.java:977)</tt><br>
<tt> at org.eclipse.core.launcher.Main.main(Main.java:952)</tt><br >
</blockquote>
<font face="Helvetica, Arial, sans-serif"><br>
<br>
<br>
</font></blockquote>
</blockquote>
</body>
</html>
--------------030500020202000005020902--
|
|
|
Goto Forum:
Current Time: Thu Sep 26 07:26:22 GMT 2024
Powered by FUDForum. Page generated in 0.05269 seconds
|