Revert of Fix hanging on browser shutdown.

Revert of Fix hanging on browser shutdown. (patchset #1 id:1 of https://codereview.chromium.org/1990453002/ )

Reason for revert:
Judging by the CL description I suspect this is causing a shutdown crash on the Linux ChromiumOS Tests (1) bot:

https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Tests%20%281%29/builds/20129

Reverting to see if that's correct.

Original issue's description:
> Fix hanging on browser shutdown.
>
> It seems that |gconf_client_*| API should be called exactly from the main thread
> (which is UI thread), for example see https://bugzilla.mozilla.org/show_bug.cgi?id=518244
>
> This CL partially reverts CL https://codereview.chromium.org/1640273002
> and makes calls to |gconf_client_*| API at the main thread.
>
> BUG=486077
>
> Committed: https://crrev.com/c7b954b3dd20dfd349de5d33468f405451452051
> Cr-Commit-Position: refs/heads/master@{#394372}

TBR=dmazzoni@chromium.org,iceman@yandex-team.ru
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=486077
Committed: https://crrev.com/44fe05658249a69e0a1c769e6d2c0e0cf7de1f1b
Cr-Commit-Position: refs/heads/master@{#394395}

[Finnur, 2016-05-18 13:00:30]

Created Revert of Fix hanging on browser shutdown.

[commit-bot: I haz the power, 2016-05-18 13:00:53]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1993763002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1993763002/1

[commit-bot: I haz the power, 2016-05-18 13:01:35]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1993763002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1993763002/1

[commit-bot: I haz the power, 2016-05-18 13:02:09]

Description was changed from

==========
Revert of Fix hanging on browser shutdown. (patchset #1 id:1 of
https://codereview.chromium.org/1990453002/ )

Reason for revert:
Judging by the CL description I suspect this is causing a shutdown crash on the
Linux ChromiumOS Tests (1) bot:

https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%...

Reverting to see if that's correct.

Original issue's description:
> Fix hanging on browser shutdown.
> 
> It seems that |gconf_client_*| API should be called exactly from the main
thread
> (which is UI thread), for example see
https://bugzilla.mozilla.org/show_bug.cgi?id=518244
> 
> This CL partially reverts CL https://codereview.chromium.org/1640273002
> and makes calls to |gconf_client_*| API at the main thread.
> 
> BUG=486077
> 
> Committed: https://crrev.com/c7b954b3dd20dfd349de5d33468f405451452051
> Cr-Commit-Position: refs/heads/master@{#394372}

TBR=dmazzoni@chromium.org,iceman@yandex-team.ru
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=486077
==========

to

==========
Revert of Fix hanging on browser shutdown. (patchset #1 id:1 of
https://codereview.chromium.org/1990453002/ )

Reason for revert:
Judging by the CL description I suspect this is causing a shutdown crash on the
Linux ChromiumOS Tests (1) bot:

https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%...

Reverting to see if that's correct.

Original issue's description:
> Fix hanging on browser shutdown.
> 
> It seems that |gconf_client_*| API should be called exactly from the main
thread
> (which is UI thread), for example see
https://bugzilla.mozilla.org/show_bug.cgi?id=518244
> 
> This CL partially reverts CL https://codereview.chromium.org/1640273002
> and makes calls to |gconf_client_*| API at the main thread.
> 
> BUG=486077
> 
> Committed: https://crrev.com/c7b954b3dd20dfd349de5d33468f405451452051
> Cr-Commit-Position: refs/heads/master@{#394372}

TBR=dmazzoni@chromium.org,iceman@yandex-team.ru
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=486077
==========

[commit-bot: I haz the power, 2016-05-18 13:02:11]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-05-18 13:03:53]

Description was changed from

==========
Revert of Fix hanging on browser shutdown. (patchset #1 id:1 of
https://codereview.chromium.org/1990453002/ )

Reason for revert:
Judging by the CL description I suspect this is causing a shutdown crash on the
Linux ChromiumOS Tests (1) bot:

https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%...

Reverting to see if that's correct.

Original issue's description:
> Fix hanging on browser shutdown.
> 
> It seems that |gconf_client_*| API should be called exactly from the main
thread
> (which is UI thread), for example see
https://bugzilla.mozilla.org/show_bug.cgi?id=518244
> 
> This CL partially reverts CL https://codereview.chromium.org/1640273002
> and makes calls to |gconf_client_*| API at the main thread.
> 
> BUG=486077
> 
> Committed: https://crrev.com/c7b954b3dd20dfd349de5d33468f405451452051
> Cr-Commit-Position: refs/heads/master@{#394372}

TBR=dmazzoni@chromium.org,iceman@yandex-team.ru
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=486077
==========

to

==========
Revert of Fix hanging on browser shutdown. (patchset #1 id:1 of
https://codereview.chromium.org/1990453002/ )

Reason for revert:
Judging by the CL description I suspect this is causing a shutdown crash on the
Linux ChromiumOS Tests (1) bot:

https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%...

Reverting to see if that's correct.

Original issue's description:
> Fix hanging on browser shutdown.
>
> It seems that |gconf_client_*| API should be called exactly from the main
thread
> (which is UI thread), for example see
https://bugzilla.mozilla.org/show_bug.cgi?id=518244
>
> This CL partially reverts CL https://codereview.chromium.org/1640273002
> and makes calls to |gconf_client_*| API at the main thread.
>
> BUG=486077
>
> Committed: https://crrev.com/c7b954b3dd20dfd349de5d33468f405451452051
> Cr-Commit-Position: refs/heads/master@{#394372}

TBR=dmazzoni@chromium.org,iceman@yandex-team.ru
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=486077

Committed: https://crrev.com/44fe05658249a69e0a1c769e6d2c0e0cf7de1f1b
Cr-Commit-Position: refs/heads/master@{#394395}
==========

[commit-bot: I haz the power, 2016-05-18 13:03:54]

Patchset 1 (id:??) landed as
https://crrev.com/44fe05658249a69e0a1c769e6d2c0e0cf7de1f1b
Cr-Commit-Position: refs/heads/master@{#394395}

[Andrey Kraynov, 2016-05-18 14:48:34]

On 2016/05/18 13:03:54, commit-bot: I haz the power wrote:
> Patchset 1 (id:??) landed as
> https://crrev.com/44fe05658249a69e0a1c769e6d2c0e0cf7de1f1b
> Cr-Commit-Position: refs/heads/master@{#394395}

Hi!

From the build bot log
(https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%...)
I see that the test was failing since May 17 (or earlier). But my CL was landed
only at 2016-05-18 09:54:57 UTC.
Could you give me an advice, how can I check if my CL is related to that test
crash?
Thanks!

[Finnur, 2016-05-18 17:07:16]

You could try reverting my revert and if the problem doesn't re-surface then you
should be good.

[Finnur, 2016-05-18 17:08:55]

Also: My sheriff shift is at an end (it's EOD here), so I advise you to work
with the sheriffs that are starting their shifts now.

[Finnur, 2016-05-18 17:08:55]

Also: My sheriff shift is at an end (it's EOD here), so I advise you to work
with the sheriffs that are starting their shifts now.