chromium-dev

[Chromium-dev] Dead Connection after crTCPIPReadExact

[<ma...@co...>]

Hi all,

When I run one of the standard chromium apps in the usual style (python
somefile.conf appname) I'm having (basically) no trouble.

But another app I'm running spits out a Dead Socket error as soon as
crappfaker starts. I've started to trace the error a bit, and it's occurring
in a __tcpip_read_exact call.


Has anyone run into this kind of thing before?


Thanks,
Jon

Re: [Chromium-dev] Dead Connection after crTCPIPReadExact

[Brian P. <bri...@tu...>]

ma...@co... wrote:
> Hi all,
> 
> When I run one of the standard chromium apps in the usual style (python
> somefile.conf appname) I'm having (basically) no trouble.
> 
> But another app I'm running spits out a Dead Socket error as soon as
> crappfaker starts. I've started to trace the error a bit, and it's occurring
> in a __tcpip_read_exact call.

Do you know if the other end of the socket connection exists, or if 
that process has terminated?


> Has anyone run into this kind of thing before?

Occasionally, when I'm developing new code or debugging, etc.

-Brian

Re: [Chromium-dev] Dead Connection after crTCPIPReadExact

[<ma...@co...>]

Brian,

> Occasionally, when I'm developing new code or debugging, etc.

:) Of course!

> Do you know if the other end of the socket connection exists, or if
> that process has terminated?

I should have given more detail...

python somefile.conf appname

appname is acutually a batch file (.bat) that sets some environment variables,
etc, and then launches the app.

The sequence of events that I'm seeing goes something like this:

1) Start mothership - everything's OK
2) Start crserver - everything's OK
3) Start appfaker - Dead Socket, appfaker exits, mothership exits

and then...

4) The app (appname) starts anyway!

So I guess that would suggest that the app process is spawning another...


To be continued...


Jon

Re: [Chromium-dev] Dead Connection after crTCPIPReadExact

[Brian P. <bri...@tu...>]

ma...@co... wrote:
> Brian,
> 
> 
>>Occasionally, when I'm developing new code or debugging, etc.
> 
> 
> :) Of course!
> 
> 
>>Do you know if the other end of the socket connection exists, or if
>>that process has terminated?
> 
> 
> I should have given more detail...
> 
> python somefile.conf appname
> 
> appname is acutually a batch file (.bat) that sets some environment variables,
> etc, and then launches the app.

A number of sci-vis apps do that sort of thing.  They're sometimes 
trouble.  Is it possible to launch the application directory without 
using the wrapper script?


> The sequence of events that I'm seeing goes something like this:
> 
> 1) Start mothership - everything's OK
> 2) Start crserver - everything's OK
> 3) Start appfaker - Dead Socket, appfaker exits, mothership exits
> 
> and then...
> 
> 4) The app (appname) starts anyway!
> 
> So I guess that would suggest that the app process is spawning another...
> 
> 
> To be continued...

-Brian