Re: Q: many broken pipes, app stops responding

On 07.07.2005, at 17:16 Uhr, Sacha Mallais wrote:

>>> This means that the connection to the browser was severed,  
>>> probably by the user hitting "Stop" or closing the browser window.
>>>
>>
>> I know - I mean, I've seen this when developing and closing the  
>> browser window too early. But - how can this bring my application  
>> to stop responding?
>>
>
> No, this exception has nothing to do with your application refusing  
> to respond.  Most likely you have a deadlock in your application  
> somewhere.  Often, this is caused by unbalanced lock()/unlock()  
> calls to EOEditingContext... is that possible?

I don't think so - I just read from the db with this app. I don't do  
any looking because of the autolocking feature of ERXEC.

cug