[Bug 39767] mission-control-5 crashed with SIGABRT in raise()

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=39767

--- Comment #3 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2011-10-03 11:30:28 PDT ---
(In reply to comment #1)
> I don't really understand the code in the client registry. It's not clear to me
> at all why the client registry should ever update the client's unique name—the
> client has its own name owner watch on the well-known name.

If I remember correctly, the idea is that the client registry tells the client
what's going on in two different situations:

* ListActivatableNames or ListNames told it that the client exists, but
  it doesn't know the unique name (and passes in NULL)
* NameOwnerChanged told it that the client exists *and* its unique name

I think the crashy case here might go something like this:

* ListActivatableNames reply says "Empathy is activatable"
* McdClientProxy created for Empathy
* GetNameOwner in the McdClientProxy wins the race with ListNames;
  McdClientProxy now knows its own unique name
* ListNames reply says "Empathy is on the bus"
* client registry tells the McdClientProxy that it is active, but
  not its unique name (because it doesn't know)
* non-NULL unique name from GetNameOwner is overwritten with NULL
* crash!

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.