|
|
|
|
|
|
|
| Re: (no subject) [message #716787 is a reply to message #716681] |
Thu, 18 August 2011 09:25   |
Eclipse User |
|
|
|
There isn't a bugzilla report regarding the OleClientSite thing I
mentioned, it's just something I was shown internally.
I don't think there's a way to increase the number of native handles
available, but unless you're on a very old Windows release, the upper
limit on handles is quite high and should not realistically be hit, even
by a big/complex app. I wonder if you're actually running into another
problem (eg.- out of memory) and SWT is throwing a NO_MORE_HANDLES
exception because a native call that should never fail is failing as a
result.
This may seem like a disconnected question, but is your app being
launched by pointing at a JRE's java executable (java.exe/javaw.exe), or
by pointing at its jvm.dll? And if you aren't specifying a "-vm"
argument at launch time then see if your app's .ini file is (eg.-
eclipse.ini). I ask because in the case with too many Browser instances
this actually proved to make a big difference; specifying -vm to point
at java.exe/javaw.exe launches a separate process, which avoids these
NO_MORE_HANDLES errors for much longer.
Grant
On 8/18/2011 12:46 AM, vijay wrote:
> The editor contains only standard controls....
> (although browser issue was new info,thanks Grant for this,is there any
> issue logged for the same)
>
> apart from coding malpractices,lets suppose say there is a genuine need
> for more controls,
> I was wondering given that there is a OS limit on handles ,what are the
> ways to increase it?
> i know swing can be used to work around this problem since there are
> many controls there,which are rendered instead of using the underlying
> controls..but then again performance overheads creep up there..
|
|
|
|
|
| Re: (no subject) [message #720984 is a reply to message #718505] |
Wed, 31 August 2011 11:17 |
| Eclipse User |
|
|
|
FWIW the Eclipse bug, including the cause of this difference, is in
https://bugs.eclipse.org/bugs/show_bug.cgi?id=356354 .
Grant
On 8/24/2011 10:03 AM, Grant Gayed wrote:
> The eclipse launcher changed at some point to load the JRE into the
> launcher's process by default. As a result if you look at the Task
> Manager you'll see a process such as eclipse.exe, but not an
> accompanying javaw.exe. When you launch an app from a running eclipse
> then javaw.exe appears in the Task Manager because the JRE is simply
> launched in a new process. There's not an obvious reason why these two
> scenarios would cause different behaviours, but the Browsers case did
> demonstrate this happening. The cause has not been determined yet.
>
> Grant
>
>
> On 8/19/2011 1:52 AM, vijay wrote:
>> Its a plain RCP application with program arguments and vmarguments,
>> the -vm argument is not there, so will try it with that and get back to
>> you with the results..(although there are no browser or OLE instances in
>> my scenario but still)
>>
>> But i thought a standalone RCP application or for that matter any java
>> application starts in its own process right?,so i am not clear what you
>> are pointing to.
>> Thanks Grant
>
|
|
|
Powered by
FUDForum. Page generated in 0.06475 seconds
Home