Fix unittest-only leak in ExtensionSettingsUIWrapper.

Fix unittest-only leak in ExtensionSettingsUIWrapper.


BUG=97511
TEST=

[not at google - send to devlin, 2011-09-22 00:59:11]

Here's another one (2 of 3).

This leak happens because those unit tests aren't processing all message loops,
so the DeleteSoon task never gets called.

This is the code way of fixing it, and it's arguably an improvement over before
(no unnecessary task posting).  I've also convinced myself it's safe to do
"synchronously".

The other option is of course to make sure that the message loops are purged in
those unit tests, but then... all unit tests need to do that from now to the
future.

[akalin, 2011-09-22 01:12:18]

On 2011/09/22 00:59:11, kalman1 wrote:
> Here's another one (2 of 3).
> 
> This leak happens because those unit tests aren't processing all message
loops,
> so the DeleteSoon task never gets called.
> 
> This is the code way of fixing it, and it's arguably an improvement over
before
> (no unnecessary task posting).  I've also convinced myself it's safe to do
> "synchronously".
> 
> The other option is of course to make sure that the message loops are purged
in
> those unit tests, but then... all unit tests need to do that from now to the
> future.

LGTM

[akalin, 2011-09-22 01:13:15]

Putting through trybots and committing from
http://codereview.chromium.org/7976043/

[akalin, 2011-09-22 05:44:56]

On 2011/09/22 01:13:15, akalin wrote:
> Putting through trybots and committing from
> http://codereview.chromium.org/7976043/

Committed as 102245