Fix issue where OpenKey() would call Close() and reset the wow64_access to 0

Fix issue where OpenKey() would call Close() and reset the wow64_access to 0 causing subsequent OpenKey() to fail.

BUG=384587
TEST=base_unittests --gtest_filter=RegistryTest.SameWowFlags

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

[grt (UTC plus 2), 2014-06-14 13:23:17]

lgtm with a small thing i noticed while looking at all calls to Close()

https://codereview.chromium.org/334973003/diff/1/base/win/registry.cc
File base/win/registry.cc (right):

https://codereview.chromium.org/334973003/diff/1/base/win/registry.cc#newcode166
base/win/registry.cc:166: wow64access_ = 0;
this is redundant. remove it?

[Will Harris, 2014-06-16 16:04:50]

cpu - seeking owner LGTM. Thanks.

https://codereview.chromium.org/334973003/diff/1/base/win/registry.cc
File base/win/registry.cc (right):

https://codereview.chromium.org/334973003/diff/1/base/win/registry.cc#newcode166
base/win/registry.cc:166: wow64access_ = 0;
On 2014/06/14 13:23:17, grt wrote:
> this is redundant. remove it?

Done.

[cpu_(ooo_6.6-7.5), 2014-06-17 16:31:13]

lgtm

[Will Harris, 2014-06-17 17:31:46]

The CQ bit was checked by wfh@chromium.org

[commit-bot: I haz the power, 2014-06-17 17:33:03]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/wfh@chromium.org/334973003/20001

[commit-bot: I haz the power, 2014-06-17 23:05:02]

Change committed as 277889