Re: Deadlock?



on 4/23/01 11:47 AM, Havoc Pennington at hp redhat com wrote:

> update_listener is oneway. My understanding is that this means the
> call isn't supposed to block waiting on the client, so there shouldn't
> be a deadlock. So that's what's supposed to happen.
> 
> If the bug is in my understanding of oneway, we are fairly well
> screwed; otherwise it's probably just some ORBit glitch.

More info. Those update_listener calls were made because of old saved state,
so they were most-likely trying to contact processes that no longer exist.

I'm not sure what to do about this problem. I just ran into it during daily
development. Nothing seems Nautilus-specific about it, and I don't know how
to reproduce it. I think it could be a real problem for GConf users.

    -- Darin





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]