DBus: Fixes a flaky test case.

DBus: Fixes a flaky test case.

In the UnregisterExportedObject test, an ExportedObject is created, destroyed
and created again as a new object. The test assumes the new object is different
from the first one just comparing the memory pointers to those objects.
Nevertheless, the memory manager could possibly alloc the same memory address
for the second object since the first one was already destroyed. This fixes
this situation preventing the first object from being destroyed incrementing
its reference count.

BUG=chromium:137846
TEST=test enabled.


Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=178450

[deymo, 2013-01-23 05:07:04]

Isn't it great when you first have a fix and suddenly you find a bug that your
fix fixes?

I think this fix a flaky test case in the DBus test suite where an object is
created, deleted, created again and checked to be different from the first one
by comparing the pointers. This could lend to a random situation where the
memory manager could alloc the second object in the same place as the (already
destroyed) first one.

keybuk, since you wrote that case, could you please review it?
satorux/stevenjb originaly reviewed the case.

Thanks =D

[keybuk, 2013-01-23 19:00:42]

lgtm

[commit-bot: I haz the power, 2013-01-23 22:25:15]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/deymo@chromium.org/12039033/1

[commit-bot: I haz the power, 2013-01-24 00:58:36]

Change committed as 178450